From 2dccdbf1b6dd720b5234faf472cb0b37a85f7df3 Mon Sep 17 00:00:00 2001 From: night-gold Date: Wed, 15 May 2019 21:29:33 +0200 Subject: [PATCH] Updated google_container_cluster (#2996) * Updated google_container_cluster Added precision on the valid subnet for 'master_ipv4_cidr_block' in 'private_cluster_config' block. * small wording tweaks + link --- 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 eb35af00..e913435f 100644 --- a/website/docs/r/container_cluster.html.markdown +++ b/website/docs/r/container_cluster.html.markdown @@ -564,7 +564,7 @@ The `private_cluster_config` block supports: * `master_ipv4_cidr_block` (Optional) - The IP range in CIDR notation to use for the hosted master network. This range will be used for assigning internal IP addresses to the master or set of masters, as well as the ILB VIP. This range must not overlap with any other ranges - in use within the cluster's network. + in use within the cluster's network, and it must be a /28 subnet. See [Limitations](https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#limitations) in the GCP docs. In addition, the `private_cluster_config` allows access to the following read-only fields: