From f9ae05165018a8060f937fd7e1fce9eb75e1ee7b Mon Sep 17 00:00:00 2001 From: Eric Chiang Date: Mon, 11 Dec 2017 11:00:36 -0800 Subject: [PATCH] securing a cluster: update language of kubelet API recommendations --- docs/tasks/administer-cluster/securing-a-cluster.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/tasks/administer-cluster/securing-a-cluster.md b/docs/tasks/administer-cluster/securing-a-cluster.md index 2b3d192a49..b95317fea6 100644 --- a/docs/tasks/administer-cluster/securing-a-cluster.md +++ b/docs/tasks/administer-cluster/securing-a-cluster.md @@ -73,11 +73,9 @@ Consult the [authorization reference section](/docs/admin/authorization/) for mo ## Controlling access to the Kubelet -Kubelets expose HTTPS endpoints which give access to data of varying sensitivity, and allow performing operations with varying levels of power on the node and within containers. +Kubelets expose HTTPS endpoints which grant powerful control over the node and containers. By default Kubelets allow unauthenticated access to this API. -By default, Kubelets allow full access to those endpoints. - -To secure access to those endpoints, enable Kubelet authentication and authorization. +Production clusters should enable Kubelet authentication and authorization. Consult the [Kubelet authentication/authorization reference](/docs/admin/kubelet-authentication-authorization) for more information.