Unverified Commit 0b3924b2 authored by Tim Hobbs's avatar Tim Hobbs Committed by GitHub
Browse files

Messages are encrypted when using TLS

When helm client and tiller use TLS their messages are encrypted, not unencrypted ;)
Showing with 1 addition and 1 deletion
+1 -1
......@@ -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).
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
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment