helm

managing secrets

Superset deployment, since it needs DB passwords, secret keys, admin credentials, etc.

👉 You should not hardcode sensitive data in values.yaml (because values.yaml usually gets committed to Git). Instead, use Kubernetes Secrets and reference them in your Helm chart.

helm repo add altinity-docs https://docs.altinity.com/clickhouse-operator helm repo update altinity-docs

helm install clickhouse-operator altinity-docs/altinity-clickhouse-operator -n operator helm list

jelm upgrade install // if we made changes in values,yml

workflow - deploying available charts

helm repo add my-release https://url
helm install my-release bitnami/nginx
helm upgrade my-release bitnami/nginx --set replicaCount=3
helm rollback my-release 1 // Reverts to a previous revision
helm uninstall my-release
helm list -A - list all releases installed 
helm repo list - list all downloaded repo
helm history <release-name> // show history
 helm show values bitnami/nginx  // print default values.yml
 helm get values <release-name> // show passed values using --set

helm get values <release-name> --all  // all default and overwrite values
 
helm show chart <chart-name> // show chart metadata
helm show all <chart-name>
use debug flag during install to get detailed logs

release-name - eg app name eg superset
revision - A revision is the version number of a release inside Kubernetes.
Every time you install, upgrade, rollback a release, Helm increments the revision number.
helm store it in configmap/secret