From 238164c4ab5a0f69695f249dfbc32e5edb0b7f36 Mon Sep 17 00:00:00 2001 From: michael saenz Date: Thu, 19 Jul 2018 19:04:53 -0500 Subject: [PATCH] update from GCE to GKE (#8881) --- .../en/docs/concepts/architecture/master-node-communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/architecture/master-node-communication.md b/content/en/docs/concepts/architecture/master-node-communication.md index 580b4d95a2a8c..652b0ac240903 100644 --- a/content/en/docs/concepts/architecture/master-node-communication.md +++ b/content/en/docs/concepts/architecture/master-node-communication.md @@ -36,7 +36,7 @@ are allowed. Nodes should be provisioned with the public root certificate for the cluster such that they can connect securely to the apiserver along with valid client -credentials. For example, on a default GCE deployment, the client credentials +credentials. For example, on a default GKE deployment, the client credentials provided to the kubelet are in the form of a client certificate. See [kubelet TLS bootstrapping](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/) for automated provisioning of kubelet client certificates.