Authorizer

Run helm charts individually

Authorizer

• Here only authorizer pod will get launch.

• Its 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 authorizer-ingress with URLs examples beta.0chain.net/authorizer01/.

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

• 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 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.