Expand the scope of the operator to AppArmor

[saschagrunert]

Loading AppArmor profiles could be done easily by the operator, too. We probably have to rename the project to something like "security-operator", too.

[saschagrunert]

cc @mrostecki

[hasheddan]

@saschagrunert @pjbgf what are y'all thinking about potential rename? Would likely be good to do sooner rather than later if it is something we want to do.

[saschagrunert]

@saschagrunert @pjbgf what are y'all thinking about potential rename? Would likely be good to do sooner rather than later if it is something we want to do.

Yes I think that's a good idea. Do you wanna go ahead and create the issue? 👍

[pjbgf]

Yep, completely agree we rather do that soon. Will create a few issues on this now.

[fejta-bot]

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

[saschagrunert]

/remove-lifecycle stale.

[fejta-bot]

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

[saschagrunert]

/remove-lifecycle rotten

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[pjbgf]

/remove-lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[pjbgf]

/remove-lifecycle stale

[pjbgf]

Initial support done via #680