From 1b49d8507c371ce58fd07402d8b0b3129fd285be Mon Sep 17 00:00:00 2001 From: johnsw87 Date: Thu, 21 Jun 2018 15:03:45 +0100 Subject: [PATCH] Update to private clusters Private clusters maintain a public IP address for kubectl to communicate with the master, the workers are internal IP addresses only. --- website/docs/r/container_cluster.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/r/container_cluster.html.markdown b/website/docs/r/container_cluster.html.markdown index 7be019c1..a4856d00 100644 --- a/website/docs/r/container_cluster.html.markdown +++ b/website/docs/r/container_cluster.html.markdown @@ -164,7 +164,7 @@ output "cluster_ca_certificate" { * `private_cluster` - (Optional, [Beta](/docs/providers/google/index.html#beta-features)) If true, a [private cluster](https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters) will be created, which makes - the master inaccessible from the public internet and nodes do not get public IP addresses either. It is mandatory to specify + the worker nodes inaccessible from the public internet and nodes do not get public IP addresses either. It is mandatory to specify `master_ipv4_cidr_block` and `ip_allocation_policy` with this option. * `project` - (Optional) The ID of the project in which the resource belongs. If it