From 0daec4717fee53352b7fb505a7f222720f75316d Mon Sep 17 00:00:00 2001 From: The Magician Date: Tue, 7 May 2024 04:25:55 -0700 Subject: [PATCH] Adding support for Cloud DNS Additive VPC Scope for GKE, currently in preview (#10590) (#18031) [upstream:d20b9dd485b908780761f82ad6a89c8fa62d592a] Signed-off-by: Modular Magician --- website/docs/r/container_cluster.html.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/r/container_cluster.html.markdown b/website/docs/r/container_cluster.html.markdown index 254eec9bdb6..473ad515907 100644 --- a/website/docs/r/container_cluster.html.markdown +++ b/website/docs/r/container_cluster.html.markdown @@ -1287,6 +1287,8 @@ linux_node_config { The `dns_config` block supports: +* `additive_vpc_scope_dns_domain` - (Optional, [Beta](https://terraform.io/docs/providers/google/guides/provider_versions.html)) This will enable Cloud DNS additive VPC scope. Must provide a domain name that is unique within the VPC. For this to work `cluster_dns = "CLOUD_DNS"` and `cluster_dns_scope = "CLUSTER_SCOPE"` must both be set as well. + * `cluster_dns` - (Optional) Which in-cluster DNS provider should be used. `PROVIDER_UNSPECIFIED` (default) or `PLATFORM_DEFAULT` or `CLOUD_DNS`. * `cluster_dns_scope` - (Optional) The scope of access to cluster DNS records. `DNS_SCOPE_UNSPECIFIED` (default) or `CLUSTER_SCOPE` or `VPC_SCOPE`.