-
Notifications
You must be signed in to change notification settings - Fork 38.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SELinuxOptions to emptyDir e2e #17577
Conversation
Labelling this PR as size/XS |
GCE e2e build/test failed for commit 1c8a4e9e6f092195ee2fea03db00817c8a51b7f1. |
This PR probably requires more thought. |
Hmm.. yeah... we need to either enable SecurityContext or not merge this. The problem is without this PR the tests will fail on systems where selinux is enabled. |
GCE e2e build/test failed for commit 8c0be8246ed636edcbe31fbf594c95c35f6f88b9. |
@pmorie could you take a look at this. It seems SecurityContext is still forbidden in the test suite. |
This enables the tests to use the kubelet's SELinux labeling. Otherwise SELinux will prevent access and the tests fail.
GCE e2e build/test failed for commit d43372b. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
@k8s-bot test this. issue #IGNORE |
GCE e2e build/test passed for commit d43372b. |
GCE e2e build/test failed for commit d43372b. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
GCE e2e build/test passed for commit d43372b. |
@swagiaal does the tests in this PR have the right labels? Do they need to be relabeled? |
@k8s-bot test this Tests are more than 48 hours old. Re-running tests. |
GCE e2e build/test passed for commit d43372b. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit d43372b. |
Automatic merge from submit-queue |
Auto commit by PR queue bot
This enables the tests to use the kubelet's SELinux labeling.
Otherwise SELinux will prevent access and the tests fail.
@pmorie