Epic Goal

Change the ConfigurationPolicy to be event driven using Kubernetes API watches by default but still allow the legacy polling option.

Why is this important?

• Should be more efficient on the API server/etcd
• For policies that manage objects that update more frequently than every 10 seconds; they will be requeued until the 10 seconds has passed to avoid starving other policies 

• The user gets immediate results when applying a configuration policy
• Policy templates that execute on the managed cluster also become event driven
• Copying an updated secret on the same cluster becomes instant
• object-templates-raw becomes more powerful
• Policies referencing the same API objects reuse the cache

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.