seccomp annotation will become non-functional in v1.27, which will be
now reflected in the documentation as well.
Ref: https://github.com/kubernetes/kubernetes/pull/114947
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
From the release notes of
https://github.com/kubernetes/kubernetes/pull/109819, we have to update
according to the following situation:
```
Action required: support for the alpha seccomp annotations
`seccomp.security.alpha.kubernetes.io/pod` and
`container.seccomp.security.alpha.kubernetes.io`, deprecated since
v1.19, has been partially removed. Kubelets no longer support the
annotations, use of the annotations in static pods is no longer
supported, and the seccomp annotations are no longer auto-populated when
pods with seccomp fields are created. Auto-population of the seccomp
fields from the annotations is planned to be removed in 1.27. Pods
should use the corresponding pod or container
`securityContext.seccompProfile` field instead.
```
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
We now update the documentation to reflect the current state of the
feature.
Refers to: https://github.com/kubernetes/enhancements/issues/2413
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Co-authored-by: Tim Bannister <tim@scalefactory.com>
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
- Highlight that we do not change the Kubernetes API and how to verify
the used seccomp profile
- Fix the kind configuration and enhance the example with a custom
workload.
Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
dancer13
Mengjiao Liu
Tim Bannister
Marcelo Giles
Andrey Goran
Sascha Grunert
Kubernetes Prow Robot
shubham82
Abigail McCarthy
carolina valencia
ydFu
windsonsea
Babapool