-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seccomp annotations name format need redefine #26610
Comments
It's not only the slash which might lead to conflicts, but also the length. The container Moving everything other than the container name to the left of the / should help. |
I can do that tomorrow (if @pmorie doesn't insist to do it himself before ;) ) |
ah good catch |
Automatic merge from submit-queue Move /seccomp/ into domain prefix in seccomp annotations Fixes #26610. /cc @mdshuai @ncdc @jfrazelle
…tations Automatic merge from submit-queue Move /seccomp/ into domain prefix in seccomp annotations Fixes kubernetes#26610. /cc @mdshuai @ncdc @jfrazelle
Now pod annotations validation only allow no more than one slash. But seccomp annotations format has more than one slash. like: security.alpha.kubernetes.io/seccomp/container/
https://github.com/kubernetes/kubernetes/blob/master/docs/design/seccomp.md#api-changes
When create a pod with seccomp annotations, it will error.
which is caused by name validation. (more than one slash)
https://github.com/kubernetes/kubernetes/blob/master/pkg/api/validation/validation.go#L92
https://github.com/kubernetes/kubernetes/blob/master/pkg/util/validation/validation.go#L38
related #25324
The text was updated successfully, but these errors were encountered: