[security] Enable pod security warnings for flux-system #2316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stefanprodan
added
area/bootstrap
|
Ref: #2014 |
pjbgf
force-pushed
the
warn-pod-security
branch
from
6a0e8bc
to
34f0d99
Compare
Signed-off-by: Paulo Gomes <paulo.gomes@weave.works>
pjbgf
force-pushed
the
warn-pod-security
branch
from
34f0d99
to
f7853c4
Compare
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable warnings for any violation of the
restrictPod Security Standard at theflux-systemnamespace. This only works when Pod Security Admission Controller is installed and enabled, which is the default setting on Kubernetesv1.23+.As of version
v0.26.0all flux components should be compatible with above mentioned policy. This is not being enforced by default to allow backwards compatibility with users that decided deploying non-flux components into theflux-systemnamespace.