You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2022. It is now read-only.
At the moment the seccomp policy uses the annotation based format to check whether a seccomp policy has been specified.
As of Kubernetes 1.19, seccomp graduated to GA and the seccomp setting migrated to securityContext (docs here).
Probably a good idea to check in both locations for the seccomp policy being specified, to avoid incorrectly flagging manifests as missing this setting.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment the seccomp policy uses the annotation based format to check whether a seccomp policy has been specified.
As of Kubernetes 1.19, seccomp graduated to GA and the seccomp setting migrated to securityContext (docs here).
Probably a good idea to check in both locations for the seccomp policy being specified, to avoid incorrectly flagging manifests as missing this setting.
The text was updated successfully, but these errors were encountered: