Skip to content

Conversation

@tchap
Copy link
Contributor

@tchap tchap commented Oct 20, 2025

Taking over #1935

There is a missing ClusterRoleBinding that should have been added with restricted-v3.

Related tests change: openshift/origin#30384

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 20, 2025

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

In response to this:

Taking over #1935

Related tests change: openshift/origin#30384

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.

@coderabbitai
Copy link

coderabbitai bot commented Oct 20, 2025

Walkthrough

Adds a new Kubernetes manifest file that creates a ClusterRoleBinding resource named system:openshift:scc:restricted-v3. The binding grants the restricted-v3 SCC ClusterRole to all authenticated subjects cluster-wide via RBAC configuration.

Changes

Cohort / File(s) Summary
New SCC RBAC Manifest
bindata/bootkube/scc-manifests/0000_20_kube-apiserver-operator_00_crb-systemauthenticated-scc-restricted-v3.yaml
Adds ClusterRoleBinding resource (rbac.authorization.k8s.io/v1) assigning the system:openshift:scc:restricted-v3 ClusterRole to the system:authenticated group with management annotations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title Check ✅ Passed The pull request title "scc: Grant authenticated users use of restricted-v3" is fully aligned with the changeset, which adds a new Kubernetes ClusterRoleBinding that assigns the restricted-v3 SCC (Security Context Constraint) role to the system:authenticated group. The title is concise, specific, and clearly conveys the primary change—granting authenticated users access to the restricted-v3 SCC. The Jira ticket reference (CNTRLPLANE-1544) adds additional context without hindering clarity.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Description Check ✅ Passed The pull request description provided by the author directly relates to the changeset. The description explicitly states that "There is a missing ClusterRoleBinding that should have been added with restricted-v3," which accurately describes what the changeset accomplishes—adding a new ClusterRoleBinding manifest file for the restricted-v3 SCC. The description provides clear context about the purpose of the change and references related work, making it meaningful and relevant to the modifications in the pull request. The description is not vague or generic; it specifically identifies what was missing and what the change adds.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2025

@tchap: This PR was included in a payload test run from openshift/origin#30384
trigger 1 job(s) of type informing for the ci release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/24061e10-adb2-11f0-8048-2ac9649c922f-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2025

@tchap: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

1 similar comment
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2025

@tchap: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2025

@tchap: This PR was included in a payload test run from openshift/origin#30384
trigger 1 job(s) of type informing for the ci release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d5531060-adb2-11f0-8c60-96d33e520b72-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2025

@tchap: This PR was included in a payload test run from openshift/origin#30384
trigger 1 job(s) of type informing for the ci release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/17c162d0-ae03-11f0-8b46-bf0a49a21fb2-0

@tchap
Copy link
Contributor Author

tchap commented Oct 20, 2025

/retest

1 similar comment
@tchap
Copy link
Contributor Author

tchap commented Oct 21, 2025

/retest

@tchap
Copy link
Contributor Author

tchap commented Oct 21, 2025

/test e2e-gcp-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 21, 2025

@tchap: This PR was included in a payload test run from openshift/origin#30384
trigger 1 job(s) of type informing for the ci release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d96286a0-ae8d-11f0-83d9-75f13b671dcf-0

@tchap
Copy link
Contributor Author

tchap commented Oct 21, 2025

/test e2e-aws-ovn

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 21, 2025

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

In response to this:

Taking over #1935

There is a missing ClusterRoleBinding that should have been added with restricted-v3.

Related tests change: openshift/origin#30384

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 21, 2025

@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue.

In response to this:

Taking over #1935

There is a missing ClusterRoleBinding that should have been added with restricted-v3.

Related tests change: openshift/origin#30384

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.

@ropatil010
Copy link

/retest

tchap added a commit to tchap/origin that referenced this pull request Oct 22, 2025
We need to include restricted-v3 scc in the list of rules for
authenticated users, but iff the associated ClusterRoleBinding exists.

This is a temporary and conditional fix to make tests passing for

openshift/cluster-kube-apiserver-operator#1944

A subsequent PR is gonna be opened once the PR above is merged.
tchap added a commit to tchap/origin that referenced this pull request Oct 22, 2025
We need to include restricted-v3 scc in the list of rules for
authenticated users, but iff the associated ClusterRoleBinding exists.

This is a temporary and conditional fix to make tests passing for

openshift/cluster-kube-apiserver-operator#1944

A subsequent PR is gonna be opened once the PR above is merged.
@tchap
Copy link
Contributor Author

tchap commented Oct 22, 2025

/payload-with-prs 4.21 ci informing openshift/origin#30384

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 22, 2025

@tchap: trigger 1 job(s) of type informing for the ci release of OCP 4.21

  • periodic-ci-openshift-release-master-ci-4.21-upgrade-from-stable-4.20-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b2df3500-af37-11f0-812a-d5b1ae1849ed-0

@tchap
Copy link
Contributor Author

tchap commented Oct 24, 2025

/retest

@tchap
Copy link
Contributor Author

tchap commented Oct 24, 2025

/verified by "[sig-auth][Feature:OpenShiftAuthorization] The default cluster RBAC policy should have correct RBAC rules"

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 24, 2025
@openshift-ci-robot
Copy link

@tchap: This PR has been marked as verified by "[sig-auth][Feature:OpenShiftAuthorization] The default cluster RBAC policy should have correct RBAC rules".

In response to this:

/verified by "[sig-auth][Feature:OpenShiftAuthorization] The default cluster RBAC policy should have correct RBAC rules"

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.

@benluddy
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Oct 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, tchap

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 Oct 24, 2025
@tchap
Copy link
Contributor Author

tchap commented Oct 24, 2025

@haircommander Do we want to cherry-pick this to 4.20?

@haircommander
Copy link
Member

Yeah I think so!
/cherry-pick release-4.20

@openshift-cherrypick-robot

@haircommander: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

Yeah I think so!
/cherry-pick release-4.20

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-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025

@tchap: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 3d6b08b link false /test okd-scos-e2e-aws-ovn

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-sigs/prow repository. I understand the commands that are listed here.

@tchap
Copy link
Contributor Author

tchap commented Oct 24, 2025

@haircommander I guess we will also need to cherry-pick the test update in origin? See the PR description.

@openshift-merge-bot openshift-merge-bot bot merged commit 151f2be into openshift:main Oct 24, 2025
14 of 15 checks passed
@openshift-cherrypick-robot

@haircommander: new pull request created: #1950

In response to this:

Yeah I think so!
/cherry-pick release-4.20

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-sigs/prow repository.

openshift-cherrypick-robot pushed a commit to openshift-cherrypick-robot/origin that referenced this pull request Nov 19, 2025
We need to include restricted-v3 scc in the list of rules for
authenticated users, but iff the associated ClusterRoleBinding exists.

This is a temporary and conditional fix to make tests passing for

openshift/cluster-kube-apiserver-operator#1944

A subsequent PR is gonna be opened once the PR above is merged.
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants