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
Copy file name to clipboardExpand all lines: website/docs/r/container_cluster.html.markdown
+2-9
Original file line number
Diff line number
Diff line change
@@ -877,16 +877,9 @@ Enables monitoring and attestation of the boot integrity of the instance. The at
877
877
878
878
*`effect` (Required) Effect for taint. Accepted values are `NO_SCHEDULE`, `PREFER_NO_SCHEDULE`, and `NO_EXECUTE`.
879
879
880
-
<aname="nested_workload_metadata_config"></a>The `workload_metadata_config`must have exactly one of `node_metadata` (deprecated) or `mode` set. This block supports:
*`node_metadata` (Optional, Deprecated) How to expose the node metadata to the workload running on the node. This is deprecated in favor of `mode`
883
-
Accepted values are:
884
-
* UNSPECIFIED: Not Set
885
-
* SECURE: Prevent workloads not in hostNetwork from accessing certain VM metadata, specifically kube-env, which contains Kubelet credentials, and the instance identity token. See [Metadata Concealment](https://cloud.google.com/kubernetes-engine/docs/how-to/metadata-proxy) documentation.
886
-
* EXPOSE: Expose all VM metadata to pods.
887
-
* GKE_METADATA_SERVER: Enables [workload identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) on the node.
888
-
889
-
*`mode` (Optional) How to expose the node metadata to the workload running on the node.
882
+
*`mode` (Required) How to expose the node metadata to the workload running on the node.
890
883
Accepted values are:
891
884
* UNSPECIFIED: Not Set
892
885
* GCE_METADATA: Expose all Compute Engine metadata to pods.
0 commit comments