Skip to content
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.

kubeaudit doesn't support initContainers #355

Closed
1 of 2 tasks
genevieveluyt opened this issue Aug 3, 2021 · 2 comments · Fixed by #376
Closed
1 of 2 tasks

kubeaudit doesn't support initContainers #355

genevieveluyt opened this issue Aug 3, 2021 · 2 comments · Fixed by #376
Assignees

Comments

@genevieveluyt
Copy link
Contributor

ISSUE TYPE
  • Bug Report
  • Feature Idea

BUG REPORT

SUMMARY

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.

ENVIRONMENT

See #285 (comment)

STEPS TO REPRODUCE

See #285 (comment)

EXPECTED RESULTS

Kubeaudit should audit initContainers the same way it audits containers.

ACTUAL RESULTS

Kubeaudit ignores initContainers and removes apparmor annotations that refer to initContainers

ADDITIONAL INFORMATION

See #285 (comment)

@danishprakash
Copy link
Contributor

@genevieveluyt I'd like to work on this, would that be okay?

@genevieveluyt
Copy link
Contributor Author

@danishprakash Please do! That would be much appreciated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants