-
Notifications
You must be signed in to change notification settings - Fork 829
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
GCP: ensure prow-build can administer KMS keys #6924
GCP: ensure prow-build can administer KMS keys #6924
Conversation
/assign @BenTheElder |
a9c1207
to
48d621e
Compare
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, pwschuurman The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is running |
Done in the main e2e pool. Still running for the rest. |
Confirming: done for all projects |
Ensure the prow-build SA use KMS keys. PDCSI e2e tests use the prow-build SA by default to authenticate against the cloudkms API.
See https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_gcp-compute-persistent-disk-csi-driver/1762/pull-gcp-compute-persistent-disk-csi-driver-e2e/1806716408805986304
This is analogous to the existing cluster IAM model, where
pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
hadroles/cloudkms.admin
permission.