-
Notifications
You must be signed in to change notification settings - Fork 101
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
Cannot create GKE Admin role permissions with current IAM Resource #381
Comments
I am getting this too, regardless of which role I try, everything fails with What am I doing wrong? Sample SA and SAPolicy:
Which causes:
|
@nielsdemoen - the assignment of the role is part of the projects api. This has not yet been implemented in provider-gcp. |
Any updates on when we expect bindings on the project's API for GCP to be implemented? Thanks in advance! |
Hey @CarpathianUA , you can use any resource that this provider doesn't have yet with provider-jet-gcp. |
@Feggah, I've tried your suggestion, and indeed version v.0.2.0-preview has implemented the resources required to add finely graded policies to Service Accounts. The only issue is that I can't fetch that version yet, since I get an Unauthorized error. We need to wait until it's publicly available. |
What do you mean by publicly available, @CalinFlorescu ? I checked that there is an image with this tag on Docker Hub, you can see it here. Isn't it enough to pull the image when you create a |
@Feggah, my apologies, I made a mistake when fetching the provider and thought that the fetch access is restricted, so my comment above isn't valid. |
@AaronME Do you have any idea what priority this issue has? |
What problem are you facing?
When we attempt to grant a ServiceAccount resource GKE Cluster Admin, we see the following error:
It appears that this role can only be assigned as a binding on the Projects api, not as a policy on a ServiceAccount.
How could Crossplane help solve your problem?
Implement bindings on the projects API for GCP.
The text was updated successfully, but these errors were encountered: