Skip to content

Conversation

tchap
Copy link
Contributor

@tchap tchap commented Oct 9, 2025

restricted-v3 annotation needs to be on the template level.
Also actually most of the securityContext fields are optional with hostUsers: false, so these are now deleted.

Aligns #580

restricted-v3 annotation needs to be on the template level.
Also actually most of the securityContext fields are optional with
hostUsers: false, so these are now deleted.
@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 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

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

In response to this:

restricted-v3 annotation needs to be on the template level. Also actually most of the securityContext fields are optional with hostUsers: false, so these are now deleted.

Aligns #580

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 9, 2025

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

In response to this:

restricted-v3 annotation needs to be on the template level.
Also actually most of the securityContext fields are optional with hostUsers: false, so these are now deleted.

Aligns #580

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 openshift-ci bot requested a review from ingvagabund October 9, 2025 13:32
@tchap tchap changed the title CNTRLPLANE-1544: manifests: Fix user namespaces for the operator CNTRLPLANE-1544: manifests: Align user namespaces for the operator Oct 9, 2025
@ingvagabund
Copy link
Member

/approve
/lgtm

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

openshift-ci bot commented Oct 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, 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 9, 2025
@tchap
Copy link
Contributor Author

tchap commented Oct 9, 2025

/hold

I am still checking with Peter Hunt how this is supposed to work. Seems to me like the scc is not being applied.

@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 Oct 9, 2025
Copy link
Contributor

openshift-ci bot commented Oct 9, 2025

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

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants