etcd-backup: modify README due to PSA #87
Conversation
This file contains hidden or 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
OpenShift manages customer workloads with the label syncer. Such that it is taken care on behalf of the user. For OpenShift namespaces, this is not true. It is expected that every team decides consciously their security posture. It is not expected that customer use that kind of namespaces!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What is this PR About?
Discourages customers to use openshift-prefixed-namespaces.
Creating an OpenShift pre-fixed namespace will break in the future, if the namespace is not labeled manually.
With the introduction of PodSecurityAdmission (PSA) namespaces will have the ability to define the security level namespace-wide.
As SCCs are more fine-grained, we defined a label syncer controller that takes care of customer workloads and sets the PSA values accordingly.
This doesn't happen for OpenShift pre-fixed namespaces as we expect that every Team working on OpenShift is defining their security posture consciously.
In addition, Helm doesn't support to create namespaces with labels.
How do we test this?
Should return labels that are set to
privileged.cc: @redhat-cop/casl