Add namespace label to align with Pod Security Admission requirements #194
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.
Fixes: #KATA-1583
- Description of the problem which is fixed/What is the use case
OpenShift 4.11 is going to enable pod security admission (https://kubernetes.io/docs/concepts/security/pod-security-admission/) using the “restricted” profile by default (https://kubernetes.io/docs/concepts/security/pod-security-standards/)
Since we require privileged support for kata-monitor, we need to label the namespace accordingly
- What I did
Added required labels to the
openshift-sandboxed-containers-operator
ns- How to verify it
Create a Kata Pod and check controller logs for
pod-security.kubernetes.io/audit-violations
.There shouldn't be any audit-violations when kata-monitor pods gets created
- Description for the changelog
Add namespace label to align with Pod Security Admission requirements