You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
container: reworked the `taint` field in `google_container_cluster` and `google_container_node_pool` to only manage a subset of taint keys based on those already in state. Most existing resources are unaffected, unless they use `sandbox_config`- see upgrade guide for details.
3
+
```
4
+
```release-note:enhancement
5
+
container: added the `effective_taints` attribute to `google_container_cluster` and `google_container_node_pool`, outputting all known taint values
to apply to nodes. This field will only report drift on taint keys that are
894
+
already managed with Terraform, use `effective_taints` to view the list of
895
+
GKE-managed taints on the node pool from all sources. Importing this resource
896
+
will not record any taints as being Terraform-managed, and will cause drift with
897
+
any configured taints. Structure is [documented below](#nested_taint).
899
898
900
899
*`workload_metadata_config` - (Optional) Metadata configuration to expose to workloads on the node pool.
901
900
Structure is [documented below](#nested_workload_metadata_config).
@@ -1310,6 +1309,8 @@ exported:
1310
1309
1311
1310
*`cluster_autoscaling.0.auto_provisioning_defaults.0.management.0.upgrade_options` - Specifies the [Auto Upgrade knobs](https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/NodeManagement#AutoUpgradeOptions) for the node pool.
1312
1311
1312
+
*`node_config.0.effective_taints` - List of kubernetes taints applied to each node. Structure is [documented above](#nested_taint).
0 commit comments