From b67d1b6f77059ae4c973380e65f1e0becbd6ea95 Mon Sep 17 00:00:00 2001 From: Tim Hobbs Date: Fri, 24 Aug 2018 18:03:23 +0200 Subject: [PATCH] Messages are encrypted when using TLS When helm client and tiller use TLS their messages are encrypted, not unencrypted ;) --- docs/securing_installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/securing_installation.md b/docs/securing_installation.md index a489cc837..454e0cc12 100644 --- a/docs/securing_installation.md +++ b/docs/securing_installation.md @@ -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