From 6d39e00e86df3ceaba2217f7d182653abb189c2c Mon Sep 17 00:00:00 2001 From: Nick Jacques Date: Fri, 22 Dec 2017 15:24:05 -0600 Subject: [PATCH] WIP: Add "internal IP only" support for Dataproc clusters (#837) * Add internalIpOnly support for Dataproc clusters * Add internal_ip_only to dataproc cluster docs * Add default/basic dataproc internal ip test case * Add test for dataproc internal_ip_only=true * fixup cluster_config.gce_cluster_config to include .0. * Remove redundant depends_on * Add %s rnd to network and subnetwork * Use variable for subnet CIDR and reference via source_ranges * Add depends_on back to dataproc cluster test * Fix cluster attribute refs (.0. again) --- docs/r/dataproc_cluster.html.markdown | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/r/dataproc_cluster.html.markdown b/docs/r/dataproc_cluster.html.markdown index 41324378acc..a6a73a2a639 100644 --- a/docs/r/dataproc_cluster.html.markdown +++ b/docs/r/dataproc_cluster.html.markdown @@ -196,6 +196,11 @@ The **cluster_config.gce_cluster_config** block supports: * `tags` - (Optional) The list of instance tags applied to instances in the cluster. Tags are used to identify valid sources or targets for network firewalls. +* `internal_ip_only` - (Optional) By default, clusters are not restricted to internal IP addresses, + and will have ephemeral external IP addresses assigned to each instance. If set to true, all + instances in the cluster will only have internal IP addresses. Note: Private Google Access + (also known as `privateIpGoogleAccess`) must be enabled on the subnetwork that the cluster + will be launched in. - - - The **cluster_config.master_config** block supports: