This repository was archived by the owner on Feb 16, 2022. It is now read-only.
This repository was archived by the owner on Feb 16, 2022. It is now read-only.
KSV030 - Doesn't trigger when no seccomp policy is specified #136
Kubernetes current default is to not set a seccomp profile on containers. At the moment KSV030 appears to only trigger when a seccomp policy or annotation is set which is not
RuntimeDefaultand does not trigger if there is no mention of seccomp in the manifest.