Make the Policy field optional and eventually deprecate/remove it from the AppArmorProfile CR

[ccojocar]

What would you like to be added:

The Policy field was originally introduced to store the raw apparmor profile installed by the operator. Later, a new field Abstract was additionally added. The later defines a detailed schema of the apparmor profile. This looks like a duplication in the API which can lead to complications and out of sync data.

At the moment, the Policy is a requied field in the AppArmorProfile CR definition. This make the Policy field mandatory, otherwise the API validation will fail before reaching the operator.

The plan is to make this optional, and use the abstract as a source for apparmor profiles. The raw profile can be generated on the fly by the operator when the Policy field is empty.

Eventually, we should deprecate and remove the policy field. Not sure, what is the impact of directly removing it. This can break the cluster where apparmor profile is installed via the Policy field.

Why is this needed:

Improve the ApparmorPolicy API by removing data duplication.

User story covered

[k8s-triage-robot]

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

[ccojocar]

/remove-lifecycle stale