Epic Goal

• Configuration Policy allows a user to declare the desired state of configuration and apply that policy to a large number of ManagedClusters. The behavior of a policy with “enforce” remediation action is to immediately push that configuration to all affected clusters. There are a number of reasons why a customer may want a more controlled approach to pushing the configuration out to the network of ManagedClusters. This proposal aims to provide users a more granular level of control on the remediation of Configuration Policy to the set of affected clusters.

• https://docs.google.com/document/d/1xnA9NF1eDmqfFp3DRSvtuJDjgrrMTfWeHDw9-rXiE1k/edit
• Goal of this Epic is to create a PolicySet to configure TALO with ACM which might get it into stable in 2.6
• maybe we support TALO only with ACM

Why is this important?

•       Customers are asking for more fine-grained rollout

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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 - Downstream documentation merged: <link to meaningful PR>