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 Oct 30, 2024. It is now read-only.
As pointed out by @thriqon in #285 (comment), kubeaudit audits containers but not initContainers. This is specifically problematic for the apparmor auditor which warns if an apparmor annotation refers to a container that doesn't exist and will remove that annotation in autofix. Since it ignores initContainers this would mean that an apparmor annotation which correctly refers to an initContainer would be removed by kubeaudit. In general though, we should add support for kubeaudit to add security controls to initContainers the same way it does for containers.
ISSUE TYPE
BUG REPORT
SUMMARY
As pointed out by @thriqon in #285 (comment), kubeaudit audits
containers
but notinitContainers
. This is specifically problematic for theapparmor
auditor which warns if an apparmor annotation refers to a container that doesn't exist and will remove that annotation inautofix
. Since it ignoresinitContainers
this would mean that an apparmor annotation which correctly refers to aninitContainer
would be removed by kubeaudit. In general though, we should add support for kubeaudit to add security controls toinitContainers
the same way it does forcontainers
.ENVIRONMENT
See #285 (comment)
STEPS TO REPRODUCE
See #285 (comment)
EXPECTED RESULTS
Kubeaudit should audit
initContainers
the same way it auditscontainers
.ACTUAL RESULTS
Kubeaudit ignores
initContainers
and removes apparmor annotations that refer toinitContainers
ADDITIONAL INFORMATION
See #285 (comment)
The text was updated successfully, but these errors were encountered: