-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Beta clusters don't automatically enable Workload Identity #490
Comments
Good point. I think we can change the node pool default to |
@sebastianneb Happy to review the PR if you are working on this. |
Just got the tests working on my machine and will quickly adapt those tomorrow and issue a PR here. |
Great remark |
CPL-markus
pushed a commit
to WALTER-GROUP/terraform-google-kubernetes-engine
that referenced
this issue
Jul 15, 2024
…usters (terraform-google-modules#490) (terraform-google-modules#512) BREAKING CHANGE: Beta clusters have changed the default to use the GKE_METADATA_SERVER, to use the old option set `node_metadata = "SECURE"`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using a beta private cluster in version
8.1.0
identity namespace gets enabled by default, but not workload identity.We delete the default node-pool after creation and use a node pool with the following basic settings:
When looking at the GCloud UI, we can see, that identity namespace for the cluster is set. Looking at the node pool we can see, that Security -> Enable GKE Metadata Server is not enabled (which is required for Workload Identity).
Looking at the code it seems like we have to set
node_metadata = "GKE_METADATA_SERVER"
on the module on our own to enable that feature.Since beta cluster should enable Identity Workload as default, this should also be the default for
node_metadata
. Also happing to issue a PR if you guys say that this is really a bug that I encounter :)The text was updated successfully, but these errors were encountered: