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
Describe the bug
the support for workload_metadata_config is missing. We want to enable workload identity in the clusters and ensure that GKE Metadata server is enabled.
The workload_metadata_config block supports:
mode (Required) How to expose the node metadata to the workload running on the node. Accepted values are:
GKE_METADATA: Run the GKE Metadata Server on this node. The GKE Metadata Server exposes a metadata API to workloads that is compatible with the V1 Compute Metadata APIs exposed by the Compute Engine and App Engine Metadata Servers. This feature can only be enabled if workload identity is enabled at the cluster level.
The text was updated successfully, but these errors were encountered:
I've mentioned to add support to default node created with standard cluster module. Is it possible to add workload_metadata_config.mode into the standard module? nodepool are using the GKE_METADATA server which is fine but default nodes created by the standard cluster is not.
Describe the bug
the support for workload_metadata_config is missing. We want to enable workload identity in the clusters and ensure that GKE Metadata server is enabled.
The workload_metadata_config block supports:
mode (Required) How to expose the node metadata to the workload running on the node. Accepted values are:
GKE_METADATA: Run the GKE Metadata Server on this node. The GKE Metadata Server exposes a metadata API to workloads that is compatible with the V1 Compute Metadata APIs exposed by the Compute Engine and App Engine Metadata Servers. This feature can only be enabled if workload identity is enabled at the cluster level.
The text was updated successfully, but these errors were encountered: