From 875aa124ce42724c2954668af86e756ebf51c81f Mon Sep 17 00:00:00 2001 From: Dana Hoffman Date: Tue, 27 Mar 2018 14:55:42 -0700 Subject: [PATCH] add gke taints --- docs/r/container_cluster.html.markdown | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/r/container_cluster.html.markdown b/docs/r/container_cluster.html.markdown index 42fc3c78af0..6218b0a7578 100644 --- a/docs/r/container_cluster.html.markdown +++ b/docs/r/container_cluster.html.markdown @@ -295,6 +295,10 @@ The `node_config` block supports: * `tags` - (Optional) The list of instance tags applied to all nodes. Tags are used to identify valid sources or targets for network firewalls. +* `taint` - (Optional, [Beta](/docs/providers/google/index.html#beta-features)) List of + [kubernetes taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) + to apply to each node. Structure is documented below. + * `workload_metadata_config` - (Optional) Metadata configuration to expose to workloads on the node pool. Structure is documented below. @@ -309,6 +313,14 @@ The `pod_security_policy_config` block supports: * `enabled` (Required) - Enable the PodSecurityPolicy controller for this cluster. If enabled, pods must be valid under a PodSecurityPolicy to be created. +The `taint` block supports: + +* `key` (Required) Key for taint. + +* `value` (Required) Value for taint. + +* `effect` (Required) Effect for taint. Accepted values are `NO_SCHEDULE`, `PREFER_NO_SCHEDULE`, and `NO_EXECUTE`. + The `workload_metadata_config` block supports: * `node_metadata` (Required) How to expose the node metadata to the workload running on the node.