This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Support in the Helm operator for connecting to Tiller with TLS Auth configured #1198
Labels
Comments
thojkooi
added a commit
to thojkooi/flux
that referenced
this issue
Jul 4, 2018
- Add support for connecting to tiller using TLS authentication. It is based on the way the helm client itself configures the TLS authentication. The default is tls disabled. - Updates the helm chart to support the TLS options. Expects the helm client certificates to be stored in a k8s secret in the same namespace as the helm-operator is deployed. The secretName can be passed along using the helm-deployment. When configuring TLS Verify, a CA certificate has to be passed and this will be created as a ConfigMap during the deployment. Closes fluxcd#1198
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We deploy our Helm set-up / Tiller with TLS Auth enabled within our clusters. We'd love to be able to have Flux use the clients certs to authenticate with Tiller.
I'm happy to work on the PR for this.
The text was updated successfully, but these errors were encountered: