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.

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

Support in spoc CLI for install /remove apparmor profiles into the local system #2387

Open
ccojocar opened this issue Jul 31, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@ccojocar
Copy link
Contributor

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 exiting ProfileManager 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

@ccojocar ccojocar added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 31, 2024
@ccojocar ccojocar changed the title Support in spoc CLI to install /remove apparmor profiles into the local system Support in spoc CLI for install /remove apparmor profiles into the local system Jul 31, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Oct 29, 2024
@ccojocar
Copy link
Contributor Author

ccojocar commented Oct 29, 2024

/remove-lifecycle stale

1 similar comment
@ccojocar
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants