-
Notifications
You must be signed in to change notification settings - Fork 119
Support in spoc CLI for install /remove apparmor profiles into the local system #2387
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.
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
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
1 similar comment
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What would you like to be added:
It would be nice to extend the spoc CLI to install apparmor profiles into the local system. The CLI is able to record apparmor profiles either as YAML definition of ApparmorProfile CR or as a raw profile. It also has the capability to distribute the recorded profiles as OCI container images but it misses any installation capability.
Currently for installation, the user still needs to run separately the
apparmor_parse
tool. It would be great to provide a seamless experience from spoc CLI.A new
install
commands can be added either to install a profile for an executable or as a named profile. The CLI can call the exitingProfileManager
interface method InstallProfile.The
remove
command can be also implemented in the same fashion.Why is this needed:
Improve the user experince when installing the apparmor profile on a local system.
User story covered
The text was updated successfully, but these errors were encountered: