0swap

Run helm charts individually

zswap

• Here 0swap, swagger & postgres pod will get launched.

• Its counts should not be changed as different pods cannot be attached to different ports. While replicas can be controlled by setting the repliCount as mentioned in values.yaml.

• Resources limits and configmap values can also be controlled by setting them in helm command.

• Create new subdomains for 0swap & swagger with 0swap.<network url> & swagger.<network url>. Example- 0swap.beta.0chain.net & swagger.beta.0chain.net.

• It will generate its own ingress with the name zswap-ingress & zswap-swagger-ingress with URLs examples 0swap.beta.0chain.net & swagger.beta.0chain.net.

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

• 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: While specifying the hostName & host in helm command it will create the complete required URL. Example: In beta.0chain.net hostName will be beta & host will be 0chain.net. Necesssary Urls will automatically get replaced in various configs/deployment files, if it is specified correctly.