From c3f03b0d08c7498e8ab2b0193cb16846dfbca0da Mon Sep 17 00:00:00 2001 From: Jared Date: Sun, 6 May 2018 14:42:59 -0700 Subject: [PATCH] Remove GKE specific content from this page https://github.com/kubernetes/website/issues/8262 --- .../concepts/architecture/master-node-communication.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/content/en/docs/concepts/architecture/master-node-communication.md b/content/en/docs/concepts/architecture/master-node-communication.md index 22ffac37bf96f..69fabb8808721 100644 --- a/content/en/docs/concepts/architecture/master-node-communication.md +++ b/content/en/docs/concepts/architecture/master-node-communication.md @@ -90,12 +90,3 @@ connection will be encrypted, it will not provide any guarantees of integrity. These connections **are not currently safe** to run over untrusted and/or public networks. -### SSH Tunnels - -[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/) uses -SSH tunnels to protect the Master -> Cluster communication paths. In this -configuration, the apiserver initiates an SSH tunnel to each node in the -cluster (connecting to the ssh server listening on port 22) and passes all -traffic destined for a kubelet, node, pod, or service through the tunnel. -This tunnel ensures that the traffic is not exposed outside of the private -GCE network in which the cluster is running.