We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems the optional check for seccomp only looks at some annotation (Which I am not sure is the right way to look for this). Kubernetes documentations says this should be set in securityContext or podSecurityContext and seems kubeaudit thinks the same. So even if I have this set like that (Without annotation, but in Context) kubescore is giving a warning. Ref: https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/seccomp.md and https://kubernetes.io/docs/tutorials/security/seccomp/
Also applying dry-run label on migration from psp to restricted psa the warining on not set vanishes when set as part of any securityContext...
/E
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It seems the optional check for seccomp only looks at some annotation (Which I am not sure is the right way to look for this). Kubernetes documentations says this should be set in securityContext or podSecurityContext and seems kubeaudit thinks the same. So even if I have this set like that (Without annotation, but in Context) kubescore is giving a warning.
Ref: https://github.com/Shopify/kubeaudit/blob/main/docs/auditors/seccomp.md and https://kubernetes.io/docs/tutorials/security/seccomp/
Also applying dry-run label on migration from psp to restricted psa the warining on not set vanishes when set as part of any securityContext...
/E
The text was updated successfully, but these errors were encountered: