CNTRLPLANE-1544: manifests: Use restricted-v3 scc for the operator#630
CNTRLPLANE-1544: manifests: Use restricted-v3 scc for the operator#630tchap wants to merge 1 commit into
Conversation
This effectively enabled user namespaces for the operator.
|
@tchap: This pull request references CNTRLPLANE-1544 which is a valid jira issue. DetailsIn response to this:
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
added
the
jira/valid-reference
|
/retest |
|
/lgtm |
openshift-ci
Bot
added
lgtm
|
@tchap is this pr still relevant ? |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: p0lyn0mial, tchap The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
|
|
@p0lyn0mial Just to be sure, this manifest is not being used by Hypershift, right? Because restricted-v3 is problematic there and I had to revert some changes there in the past... |
I don't know. @csrwng might now. @tchap let's hold this pr until we are sure :) |
|
@tchap: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
Bot
added
the
lifecycle/stale
4 participants
This effectively enabled user namespaces for the operator.