Blobber & Validator
Run helm charts individually
Blobbers & Validators
Here postgres, blobbers & validators pods will get launch. These are used for storage.
There counts can be controlled by setting the values as mentioned in values.yaml.
Resources limits and configmap values can also be controlled by setting them in helm command.
It will generate its own ingress with the name
blobber-ingress&validator-ingresswith URLs examplesbeta.0chain.net/blobber01/&beta.0chain.net/validator01/.Example for its usage in single command, you must use the namespace according to your network name. Also other values can also be set according to requirements:-
helm upgrade --install --wait -n beta blobber \ --set zminer=false \ --set blobber.hostName=helm \ --set blobber.host=0chain.net \ --set blobber.blobberCount=6 \ --set blobber.image.tag=staging \ --set blobber.config.blockWorker=https://beta.0chain.net/dns \ --set blobber.hostName=helm \ --set blobber.host=0chain.net \ --set validator.validatorCount=6 \ --set validator.image.tag=staging \ --set validator.config.blockWorker=https://beta.0chain.net/dns \ 0chain-helm/blobberNote: By default
zminer: false. It means it will deploy the blobber/validators within network. In case if it istrue, it will externally join the network.Note: By default
persistence.enabled: false. It means it will use openebs to create pvc's. In case if it istrue, it will create pv as well as pvc's.Note: By default
blobber.config.blockWorker: "http://helm-zdns-01". It is used to launch blobbers/validators within the network. Otherwise specify your domain instead ofhttp://helm-zdns-01to launch it externally & join to an existing n/w.Note: While specifying the
hostName&hostin helm command it will create theingresswith the same URLs as created in DNS. Example: Inbeta.0chain.nethostName will bebeta& host will be0chain.net. Necessary Urls will automatically get replaced in various configs/deployment files, if it is specified correctly.
Last updated