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
OCPCLOUD-1726, OCPBUGS-25654: GCP Credential Req. manifest for CAPI to use new API field #87
Conversation
Have you confirmed that this list is minimal? It's a very long list so i'd like to make sure that we do actually require each and every permission in the list. If you have, how did you do so? |
08ff780
to
c64b514
Compare
i'm curious if these permissions should look similar to the machine api related PR ? |
Yes, some of the permission are the same, but CAPI has more defined services in its interface here: https://github.com/openshift/cluster-api-provider-gcp/tree/master/cloud/services/compute Keep in mind that this is not yet tested and the e2e-gcp test job is not passing, even though I think that it might not be this change that is causing it. If you see any permission that are in your opinion extra, please let me know and I will respond why they are present in the list of permissions. |
c64b514
to
5c11370
Compare
We're leaking these custom roles created by CCO in CI so holding until we're cleaning them up. |
5c11370
to
e60cf25
Compare
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
@odvarkadaniel: This pull request references OCPCLOUD-1726 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
5efa619
to
9e1975f
Compare
/retest |
9e1975f
to
c076b3a
Compare
/hold cancel /lgtm /test all |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed 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 |
@odvarkadaniel: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-capi-operator-container-v4.16.0-202401051832.p0.gbf4db4b.assembly.stream for distgit ose-cluster-capi-operator. |
@odvarkadaniel: Jira Issue OCPBUGS-25654: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-25654 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
/cherry-pick release-4.15 |
@JoelSpeed: new pull request created: #155 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This PR removes all the
predefinedRoles
which give elevated permissions. We get those permissions and put them into the new API fieldPermissions []string
. These permissions are known to thanks to the commandgcloud iam roles describe <role>
- this lists all the included permissions we want.