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

Remove cluster role service RBAC permission leftover #1147

Conversation

rbaturov
Copy link
Contributor

@rbaturov rbaturov commented Jan 9, 2025

This PR removes the Service-related RBAC permissions previously granted in the ClusterRole.
This should have been removed as part of the #1140 backport, but it seems to have been unintentionally left behind, likely due to rebase issues.
@ffromani @Tal-or

@openshift-ci openshift-ci bot requested review from ffromani and swatisehgal January 9, 2025 11:08
* Removed the Service-related RBAC permissions previously granted in the ClusterRole

Signed-off-by: Ronny Baturov <[email protected]>
@rbaturov rbaturov force-pushed the narrow-service-permissions-4.18 branch from f792551 to 52be463 Compare January 9, 2025 11:13
Copy link
Member

@ffromani ffromani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/lgtm

please backport as needed

@@ -62,7 +62,7 @@ metadata:
}
]
capabilities: Basic Install
createdAt: "2025-01-07T08:34:09Z"
createdAt: "2025-01-09T10:45:35Z"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need to get rid of this ugly wasteful timestamp

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could have chosen not to commit this part. I wasn't sure if that was ok since I'm updating this yaml

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

every PR does that, yours is not different. We just need to stop updating the timestamp somehow.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I know. All I'm saying is that we (devs) can choose not to commit that.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 9, 2025
Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, rbaturov

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 9, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 1ef00bc into openshift-kni:release-4.18 Jan 9, 2025
15 checks passed
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants