-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add feature to define individual oauth scopes to node pools #94
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 feature to define individual oauth scopes to node pools #94
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for submitting this pull request! (And thanks for your patience on getting this review, we've been getting CI issues resolved so that we can validate pull requests like this.)
Before we dig into this change closely, I noticed that oauth scopes on node pools are no longer granted on GKE 1.10 and later. Is this pull request adding support for GKE 1.9 and older, or is there utility for oauth scopes in GKE 1.10+ that will be of continued use?
Changes look good, but CI is failing. |
Here's a copy of the current CI failures:
I bet that we can resolve this issue by adding a default value for the node_pool |
…terraform-google-kubernetes-engine into feature/node-pools-oauth-scopes
Hey folks (@adrienthebo @aaron-lane @Jberlinsky @morgante ), when can we expect it to be merged? This is a very important feature. |
92b342c
to
ab5ec5d
Compare
This LGTM, I'm going to merge into our v2.0.0 release branch. |
Recently I had a problem where some applications that use specific GCP oauth_scopes didn't recognize the scope cloud-platform (which was the default implementation of this module) as the necessary scope.
Another point is when in some situation we may need to limit scopes for some specific pools or cluster so I was thinking that may be useful to introduce manual implementation of scopes as a feature. (The default still is the cloud-platform
The module execution is similar (as in the README) as the other node_pool configuration: