[release-4.20] OCPBUGS-77005: scc: restricted-v3: Fix runAsUser range

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1947

/assign haircommander

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CNTRLPLANE-1544

Details

In response to this:

This is an automated cherry-pick of #1947

/assign haircommander

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]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[haircommander]

/retest
/lgtm

[openshift-bot]

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

[tchap]

/remove-lifecycle stale

[tchap]

/jira cherrypick OCPBUGS-77004

[openshift-ci-robot]

@tchap: Jira Issue OCPBUGS-77004 has been cloned as Jira Issue OCPBUGS-77005. Will retitle bug to link to clone.
/retitle OCPBUGS-77005: [release-4.20] CNTRLPLANE-1544: scc: restricted-v3: Fix runAsUser range

Details

In response to this:

/jira cherrypick OCPBUGS-77004

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]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77005, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #1947

/assign haircommander

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.

[tchap]

/retitle [release-4.20] OCPBUGS-77005: scc: restricted-v3: Fix runAsUser range

[tchap]

/jira refresh

[openshift-ci-robot]

@tchap: This pull request references Jira Issue OCPBUGS-77005, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-77004 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-77004 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0, 4.21.z
• bug has dependents

Requesting review from QA contact:
/cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

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]

/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, haircommander, openshift-cherrypick-robot

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [benluddy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ropatil010]

Verification: PASS
Payload: 4.20.0-0-2026-02-18-070039-test-ci-ln-zi4wsvk-latest
Cluster bot: build 4.20,#1948
Profile: ipi-on-aws/versioned-installer-ci

// Execution result:

oc get scc/restricted-v3 -o yaml | yq ".runAsUser"
type: MustRunAsRange
uidRangeMax: 65534
uidRangeMin: 1000

Create the ClusterRoleBinding kind as shown in
PR: https://github.com/openshift/cluster-kube-apiserver-operator/pull/1950

oc get deploy -n testropatil -o wide
NAME                                 READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES   SELECTOR
deployment-invalid-user-test-65535   0/1     0            0           38s   testing      ubuntu   app=testing
deployment-invalid-user-test-999     0/1     0            0           37s   testing      ubuntu   app=testing
deployment-valid-user-test-1000      1/1     1            1           36s   testing      ubuntu   app=testing
deployment-valid-user-test-65534     1/1     1            1           37s   testing      ubuntu   app=testing

oc get po -o wide -n testropatil
NAME                                                READY   STATUS    RESTARTS   AGE   IP            NODE                                       NOMINATED NODE   READINESS GATES
deployment-valid-user-test-1000-6456475846-9g9z7    1/1     Running   0          15s   10.131.0.41   ip-10-0-49-50.us-east-2.compute.internal   <none>           <none>
deployment-valid-user-test-65534-65cf89d598-h45ft   1/1     Running   0          16s   10.131.0.40   ip-10-0-49-50.us-east-2.compute.internal   <none>           <none>

oc get deploy/deployment-invalid-user-test-65535 -n testropatil -o yaml | yq ".status.conditions[].message" 
Created new replica set "deployment-invalid-user-test-65535-5bfc7558c9"
Deployment does not have minimum availability.
pods "deployment-invalid-user-test-65535-5bfc7558c9-" is forbidden: unable to validate against any security context constraint: provider restricted-v3: .containers[0].runAsUser: Invalid value: 65535: must be in the ranges: [1000, 65534]

oc get deploy/deployment-invalid-user-test-999 -n testropatil -o yaml | yq ".status.conditions[].message"
Created new replica set "deployment-invalid-user-test-999-754fc8b696"
Deployment does not have minimum availability.
pods "deployment-invalid-user-test-999-754fc8b696-" is forbidden: unable to validate against any security context constraint: provider restricted-v3: .containers[0].runAsUser: Invalid value: 999: must be in the ranges: [1000, 65534]

oc exec po/deployment-valid-user-test-1000-6456475846-9g9z7 -n testropatil -- sh -c "id"
uid=1000(ubuntu) gid=1000(ubuntu) groups=1000(ubuntu)

oc exec po/deployment-valid-user-test-65534-65cf89d598-h45ft -n testropatil -- sh -c "id"
uid=65534(nobody) gid=1000(ubuntu) groups=1000(ubuntu)

/verified by @ropatil

[openshift-ci-robot]

@ropatil010: This PR has been marked as verified by @ropatil.

Details

In response to this:

Verification: PASS
Payload: 4.20.0-0-2026-02-18-070039-test-ci-ln-zi4wsvk-latest
Cluster bot: build 4.20,#1948
Profile: ipi-on-aws/versioned-installer-ci

// Execution result:

oc get scc/restricted-v3 -o yaml | yq ".runAsUser"
type: MustRunAsRange
uidRangeMax: 65534
uidRangeMin: 1000

Create the ClusterRoleBinding kind as shown in
PR: https://github.com/openshift/cluster-kube-apiserver-operator/pull/1950

oc get deploy -n testropatil -o wide
NAME                                 READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS   IMAGES   SELECTOR
deployment-invalid-user-test-65535   0/1     0            0           38s   testing      ubuntu   app=testing
deployment-invalid-user-test-999     0/1     0            0           37s   testing      ubuntu   app=testing
deployment-valid-user-test-1000      1/1     1            1           36s   testing      ubuntu   app=testing
deployment-valid-user-test-65534     1/1     1            1           37s   testing      ubuntu   app=testing

oc get po -o wide -n testropatil
NAME                                                READY   STATUS    RESTARTS   AGE   IP            NODE                                       NOMINATED NODE   READINESS GATES
deployment-valid-user-test-1000-6456475846-9g9z7    1/1     Running   0          15s   10.131.0.41   ip-10-0-49-50.us-east-2.compute.internal   <none>           <none>
deployment-valid-user-test-65534-65cf89d598-h45ft   1/1     Running   0          16s   10.131.0.40   ip-10-0-49-50.us-east-2.compute.internal   <none>           <none>

oc get deploy/deployment-invalid-user-test-65535 -n testropatil -o yaml | yq ".status.conditions[].message" 
Created new replica set "deployment-invalid-user-test-65535-5bfc7558c9"
Deployment does not have minimum availability.
pods "deployment-invalid-user-test-65535-5bfc7558c9-" is forbidden: unable to validate against any security context constraint: provider restricted-v3: .containers[0].runAsUser: Invalid value: 65535: must be in the ranges: [1000, 65534]

oc get deploy/deployment-invalid-user-test-999 -n testropatil -o yaml | yq ".status.conditions[].message"
Created new replica set "deployment-invalid-user-test-999-754fc8b696"
Deployment does not have minimum availability.
pods "deployment-invalid-user-test-999-754fc8b696-" is forbidden: unable to validate against any security context constraint: provider restricted-v3: .containers[0].runAsUser: Invalid value: 999: must be in the ranges: [1000, 65534]

oc exec po/deployment-valid-user-test-1000-6456475846-9g9z7 -n testropatil -- sh -c "id"
uid=1000(ubuntu) gid=1000(ubuntu) groups=1000(ubuntu)

oc exec po/deployment-valid-user-test-65534-65cf89d598-h45ft -n testropatil -- sh -c "id"
uid=65534(nobody) gid=1000(ubuntu) groups=1000(ubuntu)

/verified by @ropatil

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]

/verified by @ropatil010

[openshift-ci-robot]

@ropatil010: This PR has been marked as verified by @ropatil010.

Details

In response to this:

/verified by @ropatil010

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]

/retest

[ropatil010]

/test e2e-aws-ovn

[tchap]

/retest

[tchap]

/retest

[tchap]

/retest

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-77005
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-77005 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #1947

/assign haircommander

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.