Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

/tutorials/clusters/apparmor/ says AppArmor is only supported by Docker #16478

Closed
AkihiroSuda opened this issue Sep 20, 2019 · 8 comments
Closed

/tutorials/clusters/apparmor/ says AppArmor is only supported by Docker #16478

AkihiroSuda opened this issue Sep 20, 2019 · 8 comments
Labels
language/en Issues or PRs related to English language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@AkihiroSuda
Copy link
Member

This is a Bug Report

Problem:
The website says AppArmor is only supported by Docker

Currently the only Kubernetes-supported container runtime that also supports AppArmor is Docker

If the Kubelet contains AppArmor support (>= v1.4), it will refuse to run a Pod with AppArmor options if the runtime is not Docker.

Proposed Solution:

Clarify that Kubernetes >= v1.XX supports AppArmor for non-docker CRI runtimes such as containerd/CRI >= v1.X and CRI-O >= v1.XX

Page to Update:
https://kubernetes.io/docs/tutorials/clusters/apparmor/
@savitharaghunathan
Copy link
Member

/priority backlog
/language en

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. language/en Issues or PRs related to English language labels Sep 20, 2019
@savitharaghunathan savitharaghunathan mentioned this issue Sep 25, 2019
Closed
6 tasks
@estesp
Copy link

estesp commented Oct 9, 2019

I just ran into this as well with someone claiming Docker is the only runtime implementation supporting AppArmor and had made a decision not to use containerd because of this. I would submit a PR with suggested wording fix, but that whole section on runtimes and apparmor profiles probably needs a healthy re-write and verification that it is correct.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 7, 2020
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle stale

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 6, 2020
@AkihiroSuda
Copy link
Member Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 6, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2020
@AkihiroSuda
Copy link
Member Author

Seems addressed recently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
language/en Issues or PRs related to English language lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@estesp @savitharaghunathan @AkihiroSuda @k8s-ci-robot @fejta-bot