Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for workload_metadata_config GKE_METADATA mode in standard clusters #2236

Closed
fulyagonultas opened this issue Apr 25, 2024 · 3 comments

Comments

@fulyagonultas
Copy link
Contributor

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.

@luigi-bitonti
Copy link
Contributor

@ludoo
Copy link
Collaborator

ludoo commented May 24, 2024

Closing this, feel free to reopen if @luigi-bitonti suggestion does not work.

@ludoo ludoo closed this as completed May 24, 2024
@fulyagonultas
Copy link
Contributor Author

fulyagonultas commented Aug 6, 2024

hi again,

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants