taints
Parameters
A list of Kubernetes taints to apply to nodes. GKE's API can only set this field on cluster creation. However, GKE will add taints to your nodes if you enable certain features such as GPUs. If this field is set, any diffs on this field will cause the provider to recreate the underlying resource. Taint values can be updated safely in Kubernetes (eg. through kubectl
), and it's recommended that you do not use this field to manage taints. If you do, lifecycle.ignore_changes
is recommended. Structure is documented below.
Parameters
A list of Kubernetes taints to apply to nodes. GKE's API can only set this field on cluster creation. However, GKE will add taints to your nodes if you enable certain features such as GPUs. If this field is set, any diffs on this field will cause the provider to recreate the underlying resource. Taint values can be updated safely in Kubernetes (eg. through kubectl
), and it's recommended that you do not use this field to manage taints. If you do, lifecycle.ignore_changes
is recommended. Structure is documented below.
Parameters
A list of Kubernetes taints to apply to nodes. GKE's API can only set this field on cluster creation. However, GKE will add taints to your nodes if you enable certain features such as GPUs. If this field is set, any diffs on this field will cause the provider to recreate the underlying resource. Taint values can be updated safely in Kubernetes (eg. through kubectl
), and it's recommended that you do not use this field to manage taints. If you do, lifecycle.ignore_changes
is recommended. Structure is documented below.