Keygen
Run helm charts individually
Keygen
Keygen is used to create keys for miners, sharders, blobbers, zbox-keys, nodes, & authorizer.
Keygen is a job that runs and complete after successful executions. Keys generation inside the pod takes time you can look into the script how keys are being copied & configmaps are generated from them.
Keys counts can be controlled by setting the values as mentioned in values.yaml
PUBLIC_ENDPOINT=
beta.0chain.netwill automatically get generated when keygen.hostName is set tobeta& host to0chain.netfrom values.yaml.Set the hostname according to the subdomain to be used Example:-
helm upgrade --install --wait -n beta keygen \ --set keygen.hostName=beta \ --set keygen.host=0chain.net \ --set keygen.env.MINER="3" \ --set keygen.env.SHARDER="2" \ --set keygen.env.BLOBBER="6" \ --set keygen.env.VALIDATOR="6" \ --set keygen.env.AUTHORIZER="1" \ 0chain-helm/keygenNote: While specifying the namespace in helm command it should same as subdomain i.e. created in DNS. Example: In
beta.0chain.netnamespace will bebeta. Necesssary Urls will automatically get replaced in various configs/deployment files, if it is specified correctly.
Last updated