Skip to content
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

odvarkadaniel
Copy link
Contributor

This PR removes all the predefinedRoles which give elevated permissions. We get those permissions and put them into the new API field Permissions []string. These permissions are known to thanks to the command gcloud iam roles describe <role> - this lists all the included permissions we want.

@JoelSpeed
Copy link
Contributor

this lists all the included permissions we want.

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?

@odvarkadaniel odvarkadaniel force-pushed the gcp-capi-cred-req-manifest-to-use-permissions-field branch 4 times, most recently from 08ff780 to c64b514 Compare November 30, 2022 10:12
@elmiko
Copy link
Contributor

elmiko commented Nov 30, 2022

i'm curious if these permissions should look similar to the machine api related PR ?

@odvarkadaniel
Copy link
Contributor Author

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.

@odvarkadaniel odvarkadaniel force-pushed the gcp-capi-cred-req-manifest-to-use-permissions-field branch from c64b514 to 5c11370 Compare December 6, 2022 14:27
@abutcher
Copy link
Member

abutcher commented Dec 9, 2022

We're leaking these custom roles created by CCO in CI so holding until we're cleaning them up.
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 9, 2022
@odvarkadaniel odvarkadaniel force-pushed the gcp-capi-cred-req-manifest-to-use-permissions-field branch from 5c11370 to e60cf25 Compare December 15, 2022 11:48
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 16, 2023
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 15, 2023
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jul 16, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 16, 2023

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

@JoelSpeed JoelSpeed reopened this Nov 24, 2023
@JoelSpeed
Copy link
Contributor

/retest

@JoelSpeed JoelSpeed changed the title [OCPCLOUD-1726]: GCP Credential Req. manifest for CAPI to use new API field OCPCLOUD-1726: GCP Credential Req. manifest for CAPI to use new API field Dec 13, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 13, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 13, 2023

@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:

This PR removes all the predefinedRoles which give elevated permissions. We get those permissions and put them into the new API field Permissions []string. These permissions are known to thanks to the command gcloud iam roles describe <role> - this lists all the included permissions we want.

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.

@JoelSpeed JoelSpeed force-pushed the gcp-capi-cred-req-manifest-to-use-permissions-field branch from 5efa619 to 9e1975f Compare December 18, 2023 14:07
@jstuever
Copy link

/retest

@JoelSpeed JoelSpeed force-pushed the gcp-capi-cred-req-manifest-to-use-permissions-field branch from 9e1975f to c076b3a Compare January 4, 2024 13:11
@JoelSpeed
Copy link
Contributor

/hold cancel

/lgtm
/approve

/test all

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 5, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2024
Copy link
Contributor

openshift-ci bot commented Jan 5, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD be94864 and 2 for PR HEAD c076b3a in total

Copy link
Contributor

openshift-ci bot commented Jan 5, 2024

@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.

@openshift-merge-bot openshift-merge-bot bot merged commit bf4db4b into openshift:main Jan 5, 2024
14 checks passed
@openshift-bot
Copy link

[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.
All builds following this will include this PR.

@JoelSpeed JoelSpeed changed the title OCPCLOUD-1726: GCP Credential Req. manifest for CAPI to use new API field OCPCLOUD-1726, OCPBUGS-25654: GCP Credential Req. manifest for CAPI to use new API field Jan 8, 2024
@openshift-ci-robot
Copy link

@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:

This PR removes all the predefinedRoles which give elevated permissions. We get those permissions and put them into the new API field Permissions []string. These permissions are known to thanks to the command gcloud iam roles describe <role> - this lists all the included permissions we want.

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.

@JoelSpeed
Copy link
Contributor

/cherry-pick release-4.15

@openshift-cherrypick-robot

@JoelSpeed: new pull request created: #155

In response to this:

/cherry-pick release-4.15

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants