UPSTREAM: 106454: SQUASH: test/e2e: let e2e tests specify pod security admiss…#1128
Conversation
|
@s-urbaniak: 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:
Comment |
|
/test unit |
c1c2546 to
e7a6c0f
Compare
|
@s-urbaniak: 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:
Comment |
e7a6c0f to
0a6f238
Compare
|
@s-urbaniak: 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:
Comment |
|
@s-urbaniak: 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:
Comment |
|
/test required |
|
@s-urbaniak: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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 kubernetes/test-infra repository. |
|
/retest-required |
|
@s-urbaniak: 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:
Comment |
98cdc93 to
353c98c
Compare
|
@s-urbaniak: 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:
Comment |
done |
…ion configuration
353c98c to
542e1f8
Compare
|
@s-urbaniak: 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:
Comment |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, s-urbaniak, stlaz 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 |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/test e2e-aws-serial |
|
/test e2e-gcp |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@s-urbaniak: The following test failed, say
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/test-infra repository. I understand the commands that are listed here. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Currently, e2e tests don't know about PodSecurity Admission. This introduces the possibility to specify namespace labels for tests.
Additionally, it sets a default set of policies for e2e test namespaces bound to
restricted.Finally, it makes a first pass of identified e2e tests which deploy privileged workloads.