[WIP] OCPBUGS-64663 runAsUser/runAsGroup not behaving to the expected range values in user namespaces

[ropatil010]

Hi Team,

Can you PTAL for this PR.

Without this PR: There is no proper message to user why the deployment is not in ready state.
https://issues.redhat.com/browse/OCPBUGS-64663

Try to create deployment with value runAsGroup: 65536

oc get deploy -n testropatil
NAME READY UP-TO-DATE AVAILABLE AGE
deployment-invalid-group-test-65536 0/1 1 0 57m

Check output message:
oc get deploy/deployment-invalid-group-test-65536 -n testropatil -o yaml
hostUsers: false
restartPolicy: Always
schedulerName: default-scheduler
securityContext:
fsGroup: 1000
runAsGroup: 65536
runAsNonRoot: true
runAsUser: 1000
seccompProfile:
type: RuntimeDefault
terminationGracePeriodSeconds: 30
status:
conditions:

• lastTransitionTime: "2025-11-05T05:50:19Z"
  lastUpdateTime: "2025-11-05T05:50:19Z"
  message: Deployment does not have minimum availability.
  reason: MinimumReplicasUnavailable
  status: "False"
  type: Available
• lastTransitionTime: "2025-11-05T05:50:19Z"
  lastUpdateTime: "2025-11-05T05:50:19Z"
  message: ReplicaSet "deployment-invalid-group-test-65536-75474b4bdf" is progressing.
  reason: ReplicaSetUpdated
  status: "True"
  type: Progressing
  observedGeneration: 1
  replicas: 1
  unavailableReplicas: 1
  updatedReplicas: 1

With PR:
When try to create deployment with invalid max value: 65536 it wont creates the deployment and gives below info/message
oc create -f deployment-invalid-group-test-65536.yaml
Will get message info as:
The Deployment "deployment-invalid-group-test-65536" is invalid: spec.template.spec.securityContext.runAsGroup: Invalid value: 65536: must be between 0 and 65535 when user namespaces are enabled (hostUsers=false)

/hold

[openshift-ci-robot]

@ropatil010: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 4d7a50f|testing scc checks: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ropatil010
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[openshift-ci-robot]

@ropatil010: the contents of this pull request could be automatically validated.

The following commits are valid:

• 4b816f9|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[ropatil010]

/unhold

[ropatil010]

This is just a partial fix for max range, we can add RFE for runAsGroup when we enter the value: 999(min value).

[openshift-ci-robot]

@ropatil010: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 4b816f9|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 6f9608f|add cases: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@ropatil010: the contents of this pull request could be automatically validated.

The following commits are valid:

• 4b816f9|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged
• ebf29c1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups_2: the upstream PR kubernetes/kubernetes#1234 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[ropatil010]

/test-with openshift/apiserver-library-go#154

[openshift-ci-robot]

@ropatil010: the contents of this pull request could be automatically validated.

The following commits are valid:

• 35494ab|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups_3: the upstream PR kubernetes/kubernetes#1234 has merged
• 4b816f9|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged
• ebf29c1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups_2: the upstream PR kubernetes/kubernetes#1234 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@ropatil010: the contents of this pull request could be automatically validated.

The following commits are valid:

• c8d85b1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[ropatil010]

/retitle OCPBUGS-64663 runAsUser/runAsGroup not behaving to the expected range values in user namespaces

[ropatil010]

Execution result:

When try to create deployment with invalid user/group(after 64534+) id, it gives error that it must be in the ranges: [1000, 65534]
Deployment.apps "deployment-invalid-group-test-65535" is invalid: spec.template.spec.securityContext.runAsGroup: Invalid value: 65535: must be between 0 and 65535 when user namespaces are enabled (hostUsers=false)
Deployment.apps "deployment-invalid-user-test-65535" is invalid: spec.template.spec.securityContext.runAsUser: Invalid value: 65535: must be between 0 and 65535 when user namespaces are enabled (hostUsers=false)

[ropatil010]

Just for reference: https://issues.redhat.com/browse/CNTRLPLANE-1909

[openshift-ci-robot]

@ropatil010: the contents of this pull request could not be automatically validated.

The following commits are valid:

• c8d85b1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

The following commits could not be validated and must be approved by a top-level approver:

• b3245b3|testing: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[ropatil010]

/hold

[openshift-ci-robot]

@ropatil010: the contents of this pull request could be automatically validated.

The following commits are valid:

• 1e8ff72|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups2: the upstream PR kubernetes/kubernetes#1234 has merged
• c8d85b1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@ropatil010: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 1e8ff72|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups2: the upstream PR kubernetes/kubernetes#1234 has merged
• c8d85b1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 521c397|change default: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@ropatil010: the contents of this pull request could not be automatically validated.

The following commits are valid:

• 1e8ff72|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups2: the upstream PR kubernetes/kubernetes#1234 has merged
• c8d85b1|UPSTREAM: 1234: Fix user namespace validation for runAsGroup, fsGroup, and supplementalGroups: the upstream PR kubernetes/kubernetes#1234 has merged

The following commits could not be validated and must be approved by a top-level approver:

• 521c397|change default: does not specify an upstream backport in the commit message
• 8b27caf|add mustrunasrange: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

@ropatil010: The following tests 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/e2e-aws-ovn-techpreview-serial-1of2	8b27caf	link	false	/test e2e-aws-ovn-techpreview-serial-1of2
ci/prow/e2e-aws-crun-wasm	8b27caf	link	true	/test e2e-aws-crun-wasm
ci/prow/verify-commits	8b27caf	link	true	/test verify-commits
ci/prow/e2e-metal-ipi-ovn-ipv6	8b27caf	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-gcp	8b27caf	link	true	/test e2e-gcp
ci/prow/e2e-aws-ovn-runc	8b27caf	link	true	/test e2e-aws-ovn-runc
ci/prow/e2e-aws-ovn-fips	8b27caf	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-techpreview-serial-2of2	8b27caf	link	false	/test e2e-aws-ovn-techpreview-serial-2of2
ci/prow/e2e-aws-ovn-serial-1of2	8b27caf	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/k8s-e2e-gcp-serial	8b27caf	link	true	/test k8s-e2e-gcp-serial
ci/prow/verify	8b27caf	link	true	/test verify
ci/prow/k8s-e2e-gcp-ovn	8b27caf	link	true	/test k8s-e2e-gcp-ovn
ci/prow/e2e-aws-ovn-techpreview	8b27caf	link	false	/test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-cgroupsv2	8b27caf	link	true	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-serial-2of2	8b27caf	link	true	/test e2e-aws-ovn-serial-2of2
ci/prow/k8s-e2e-conformance-aws	8b27caf	link	true	/test k8s-e2e-conformance-aws
ci/prow/e2e-aws-ovn-hypershift	8b27caf	link	true	/test e2e-aws-ovn-hypershift
ci/prow/unit	8b27caf	link	true	/test unit
ci/prow/e2e-aws-ovn-crun	8b27caf	link	true	/test e2e-aws-ovn-crun

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

[openshift-bot]

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-merge-robot]

PR needs rebase.

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.

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

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f439576b-8997-4e2c-a0c2-44640d941bb5

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

📝 Coding Plan

• Generate coding plan for human review comments

---

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