You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2021. It is now read-only.
Thank you so much for creating this plugin! The team I'm on started using this plugin last week, and it's working great.
Before we found this plugin, we looked into securing tiller by enabling TLS. Now after having explored both of those options (as ways to not have an unsecure/open endpoint in our K8s clusters), it seems like going tillerless is way easier than setting up a pipeline to maintain/update *.pem certs for TLS. (I wonder if this plugin can/should be mentioned on https://github.com/helm/helm/blob/master/docs/securing_installation.md...)
The only minor gotcha I ran into (when working through the steps described on https://rimusz.net/tillerless-helm/) is we sometimes do helm repo add, which (even when using this plugin) requires that helm init --client-only has been done. So perhaps it would be helpful to add mention of that to the blog post.
The text was updated successfully, but these errors were encountered:
Thank you so much for creating this plugin! The team I'm on started using this plugin last week, and it's working great.
Before we found this plugin, we looked into securing tiller by enabling TLS. Now after having explored both of those options (as ways to not have an unsecure/open endpoint in our K8s clusters), it seems like going tillerless is way easier than setting up a pipeline to maintain/update
*.pem
certs for TLS. (I wonder if this plugin can/should be mentioned on https://github.com/helm/helm/blob/master/docs/securing_installation.md...)The only minor gotcha I ran into (when working through the steps described on https://rimusz.net/tillerless-helm/) is we sometimes do
helm repo add
, which (even when using this plugin) requires thathelm init --client-only
has been done. So perhaps it would be helpful to add mention of that to the blog post.The text was updated successfully, but these errors were encountered: