From c1beb824c43e7173a57ddf3015ece6c4ae91e09d Mon Sep 17 00:00:00 2001 From: Matt Braymer-Hayes Date: Sat, 24 Feb 2018 13:13:46 -0800 Subject: [PATCH] Update master-node-communication.md (#7467) Remove out-of-date reference to TODO (#7314). --- docs/concepts/architecture/master-node-communication.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/docs/concepts/architecture/master-node-communication.md b/docs/concepts/architecture/master-node-communication.md index 57e6f860ad..ee957de22e 100644 --- a/docs/concepts/architecture/master-node-communication.md +++ b/docs/concepts/architecture/master-node-communication.md @@ -43,13 +43,7 @@ The `kubernetes` service (in all namespaces) is configured with a virtual IP address that is redirected (via kube-proxy) to the HTTPS endpoint on the apiserver. -The master components communicate with the cluster apiserver over the -insecure (not encrypted or authenticated) port. This port is typically only -exposed on the localhost interface of the master machine, so that the master -components, all running on the same machine, can communicate with the -cluster apiserver. Over time, the master components will be migrated to use -the secure port with authentication and authorization (see -[#13598](https://github.com/kubernetes/kubernetes/issues/13598)). +The master components also communicate with the cluster apiserver over the secure port. As a result, the default operating mode for connections from the cluster (nodes and pods running on the nodes) to the master is secured by default