See ACM-14827 for more context.

We should also design to refactor the status-sync to use the policy statuses directly rather than Kubernetes events.

mprahl's top of mind options:

Store the last 10 compliance events to the status of each ConfigurationPolicy/CertificatePolicy/OperatorPolicy like we do for Policy.

1. 1. Benefits:
      1. Works with Discovered policies
      2. Allows the policy framework to move away from using Kubernetes events for status communication which occasionally leads to the Policy status being out of sync with the ConfigurationPolicy
      3. Similar experience to Policy

1. 1. Downsides:
      1. It requires that we have control over the CRD so it’d be specific to OCM-io policies.