-
Notifications
You must be signed in to change notification settings - Fork 189
kubeaudit does not understand PodSecurityContext.seccompProfile #343
Comments
Hey @dmitry-irtegov , thanks for bringing this up and providing a detailed example! This sounds like something we definitely want to support |
Hey @genevieveluyt, mind If I take a look at this? |
@danishprakash Did you ever take a look at this? |
Hi @genevieveluyt , I'm planning to fix this issue. I'm wondering if I should do a breaking change with kubeaudit to support |
(FWIW the |
Hey @danishprakash and @Ser87ch , sorry I missed your messages! Been getting too many Dependabot notifications drowning out important ones 😢 . Thank you @Ser87ch for opening a PR, I will take a look! |
ISSUE TYPE
BUG REPORT
SUMMARY
In k8s 1.20 was introduced GA syntax for setting seccompProfile:
When running kubeaudit on pods with this setting, it complains about SeccompAnnotationMissing
ENVIRONMENT
STEPS TO REPRODUCE
Deploy the kubernetes-dashboard according with https://github.com/kubernetes/dashboard/blob/master/aio/deploy/recommended.yaml, but the daemonset spec modified as follows:
Run kubeaudit by applying the following manifest:
EXPECTED RESULTS
Kubeaudit complains about AppArmorAnnotationMissing but not about SeccompAnnotationMissing.
ACTUAL RESULTS
ADDITIONAL INFORMATION
The text was updated successfully, but these errors were encountered: