gce: Update GCE storage service scope to DevstorageFullControlScope to resolve permission error. #16355
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a fix for the functionality added in #16050.
In some cases, kops was unable to query the GCP API to retrieve the bucket IAM policy.
The API would return a 403 Forbidden.
e.g.
This PR increases the auth scopes that the GCS client is created with to resolve the permission problem
Strangely this 403 error did not happen until kops was authenticating to GCS using a Service Account created in a different GCP project than where the OIDC Issuer bucket was created.