✨ leave the pod.spec.containers[0].capabilities.DROP.All uncommented by default #2767
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.
Description
leave the pod.spec.containers[0].capabilities.DROP.All uncommented by default
Motivation
Kubernetes API has been changing, and the PodSecurityPolicy API is deprecated and will no longer be served from k8s 1.25. This API is replaced by a new built-in admission controller (KEP-2579: Pod Security Admission Control) which allows cluster admins to enforce the Pod Security Standards with Namespace Labels.
What are the changes?
With the introduction of Pod Security Admission, Namespace and Pod/Containers can be defined with three different policies which are; Privileged, Baseline and Restricted. (More info). Therefore, Pods/Containers that are not configured according to the enforced security standards defined globally or on the namespace level will not be admitted and will not be able to run.
So, let's keep commenting only seccompProfile since it does not work in all clusters.