I’m using Helm for managing apps running in my Kubernetes cluster. I’m managing multiple clusters for different environments. kubectl
supports this out of the box, e.g.:
kubectl config set-context staging
kubectl config set-context production
To each cluster belongs a specific Helm configurarion.
2 environment variables:
TILLER_NAMESPACE
HELM_TLS_ENABLE
And in case HELM_TLS_ENABLE
is true, also a PEM certificate and key.
Currently when I switch context, I need to change the Helm related variables manually. Is there a way to automate this? I imagined maybe a hook that’s called when the kubectl
context is changed, but I couldn’t really find a way.
A ZSH specific option is also acceptable, although a shell agnostic method is preferred.
Best Answer
Posting this answer as a community wiki to point to the comments made under the question and to add additional information.
Feel free to expand.
This issue is now to be considered irrelevant. The question was specific on the following environment variables:
TILLER_NAMESPACE
HELM_TLS_ENABLE
Focusing specifically on
tiller
:Helm v2
which was usingtiller
is now deprecated.Helm v3
does not usetiller
anymore.Citing the official documentation on support skew:
Additional resources: