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

Support AppArmor profile unconfined #442

Closed
1 of 2 tasks
JWT95 opened this issue Jun 10, 2022 · 2 comments · Fixed by #489
Closed
1 of 2 tasks

Support AppArmor profile unconfined #442

JWT95 opened this issue Jun 10, 2022 · 2 comments · Fixed by #489

Comments

@JWT95
Copy link

JWT95 commented Jun 10, 2022

ISSUE TYPE
  • Bug Report
  • Feature Idea

FEATURE IDEA

Proposal: At current kubeaudit does not support annotations of the form: container.apparmor.security.beta.kubernetes.io/<container>: unconfined. It errors with: Message: AppArmor is disabled. This can't be overriden because kubeaudit doesn't support apparmor override errors.

But the unconfined profile is supported by k8s and may be used for containers that need access to /proc but can't use localhost profiles.

kubeaudit should either support the unconfined profile or allow overrides for apparmor. I think the same applies for seccomp.

@ghost
Copy link

ghost commented Jun 10, 2022

Thanks for opening your first issue here! Be sure to follow the issue template!

@genevieveluyt
Copy link
Contributor

genevieveluyt commented Jun 10, 2022

Why not both? 🙂 If you are interested in contributing, we would be happy to accept this change.

EDIT: Actually, since unconfined runs apparmor with no security profile, I think we want to discourage this. We should introduce an override label.

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

Successfully merging a pull request may close this issue.

2 participants