From eb2722e2cb143574a9d7dce4c294dbb4a9ca5628 Mon Sep 17 00:00:00 2001 From: lihuang Date: Mon, 5 Feb 2018 13:26:40 +0800 Subject: [PATCH] Update securing_installation.md --- 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 38350a922..7bb84a1d8 100644 --- a/docs/securing_installation.md +++ b/docs/securing_installation.md @@ -45,7 +45,7 @@ Tiller in its current form does not provide a way to map user credentials to spe To properly limit what Tiller itself can do, the standard Kubernetes RBAC mechanisms must be attached to Tiller, including Roles and RoleBindings that place explicit limits on what things a Tiller instance can install, and where. -This situation may change in the future. While the community has several methods that might address this, at the moment performing actions using the rights of the client, instead of the rights of Tiller, is contingent upon the outcome of the Pod Identity Working Group, which has taken on the task of solving the problem in a general way. +This situation may change in the future. While the community has several methods that might address this, at the moment performing actions using the rights of the client, instead of the rights of Tiller, is contingent upon the outcome of the Pod Identity Working Group, which has taken on the task of solving the problem general. ### The Tiller gRPC Endpoint and TLS