e2e: add podsecurity labels #405
Conversation
openshift-merge-robot
added
the
needs-rebase
openshift-ci
bot
added
the
do-not-merge/work-in-progress
openshift-merge-robot
removed
the
needs-rebase
openshift-ci
bot
added
the
approved
OCP >= 4.12 wants to have stricter podsecurity rules. In our e2e tests we do a bunch of stuff, including running privileged pods. We just annotate the test namespace(s) to signal we need top privileges. Since e2e tests run in very controlled envs (CI mostly), and since test namespace should be gone anyway once the e2e tests are finished, this is still fair game. Signed-off-by: Francesco Romani <fromani@redhat.com>
ffromani
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fromanirh, MarSik 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 |
|
/retest-required |
|
/lgtm |
|
likely same issue as #408 (comment) |
|
@fromanirh: 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/test-infra repository. I understand the commands that are listed here. |
|
/cherry-pick release-4.11 |
|
@fromanirh: new pull request created: #457 In 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 kubernetes/test-infra repository. |
OCP >= 4.12 wants to have stricter podsecurity rules. In our e2e tests we do a bunch of stuff, including running privileged pods. We just annotate the test namespace(s) to signal we need top privileges. Since e2e tests run in very controlled envs (CI mostly), and since test namespace should be gone anyway once the e2e tests are finished, this is still fair game. Signed-off-by: Francesco Romani <fromani@redhat.com>
OCP >= 4.12 wants to have stricter podsecurity rules. In our e2e tests we do a bunch of stuff, including running privileged pods. We just annotate the test namespace(s) to signal we need top privileges. Since e2e tests run in very controlled envs (CI mostly), and since test namespace should be gone anyway once the e2e tests are finished, this is still fair game. Signed-off-by: Francesco Romani <fromani@redhat.com>
OCP >= 4.12 wants to have stricter podsecurity rules.
In our e2e tests we do a bunch of stuff, including running privileged pods. We just annotate the test namespace(s) to signal we need top privileges. Since e2e tests run in very controlled envs (CI mostly), and since test namespace should be gone anyway once the e2e tests are finished, this is still fair game.
Signed-off-by: Francesco Romani fromani@redhat.com