0box

Run helm charts individually

0box

• Here zbox, postgres & swagger pod will get launch.

• For one network only one 0box is needed. So, there no need to increase its count. Other things 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 zbox-ingress with URLs examples 0box.beta.0chain.net & 0box.beta.0chain.net/swagger/.

• 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 0box \
      --set zbox.hostName=beta \
      --set zbox.host=0chain.net \
      --set zbox.image.tag=staging \
      --set zbox.config.blockWorker=https://beta.0chain.net/dns \
      --set zbox.config.stripe.webhookSecret=whsec_VfwFUOxFIxw5RP1fWMA6ai38EYHAvUDL \
      0chain-helm/zbox

• Note: By default persistence.enabled: false. It means it will use openebs to create pvc's. In case if it is true, it will create pv as well as pvc's.

• Note: By default zbox.config.blockWorker: "http://helm-zdns-01". It is used to stake blobbers within the network. Otherwise specify your domain instead of http://helm-zdns-01 to launch it externally & join to an existing n/w.

• Note: While specifying the hostName & host in helm command it will create the ingress with the same URLs as created in DNS. Example: In beta.0chain.net hostName will be beta & host will be 0chain.net. Necessary Urls will automatically get replaced in various configs/deployment files, if it is specified correctly.