msb-public
/
helm
mirror of https://github.com/helm/helm
1
0
Code Issues Projects Releases Wiki Activity

Messages are encrypted when using TLS

Browse Source 
When helm client and tiller use TLS their messages are encrypted, not unencrypted ;)
pull/4529/head
Tim Hobbs 6 years ago committed by GitHub
parent 78550dd2c8
commit 0b3924b2ac
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
docs/securing_installation.md
Unescape View File

@ -57,7 +57,7 @@ Shared and production clusters -- for the most part -- should use Helm 2.7.2 at
For more information about the proper steps to configure Tiller and use Helm properly with TLS configured, see [Using SSL between Helm and Tiller](tiller_ssl.md). For more information about the proper steps to configure Tiller and use Helm properly with TLS configured, see [Using SSL between Helm and Tiller](tiller_ssl.md).
When Helm clients are connecting from outside of the cluster, the security between the Helm client and the API server is managed by Kubernetes itself. You may want to ensure that this link is secure. Note that if you are using the TLS configuration recommended above, not even the Kubernetes API server has access to the unencrypted messages between the client and Tiller. When Helm clients are connecting from outside of the cluster, the security between the Helm client and the API server is managed by Kubernetes itself. You may want to ensure that this link is secure. Note that if you are using the TLS configuration recommended above, not even the Kubernetes API server has access to the encrypted messages between the client and Tiller.
### Tiller's Release Information ### Tiller's Release Information

Write Preview
Loading…
Cancel
Save