kubernetes: replace deprecated seccomp annotations with securityContext #1052
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.
Kubernetes added the official
securityContext.seccompProfile
support in Kubernetes 1.19.Seccomp is still disabled by default.
The legacy
container.seccomp.security.alpha.kubernetes.io/<PODNAME>
annotation has been deprecated and will be unsupported in Kubernetes 1.25.https://kubernetes.io/docs/tutorials/security/seccomp/
A test cluster can be created with the following minikube command:
Related to: