Value Statement

As an ACM policy user, I have unicorn clusters that don’t behave like the rest so I need a way to still rollout the policy to them but not block on their status so that other clusters can continue in the rollout.

Definition of Done for Engineering Story Owner (Checklist)

• We are currently thinking of adding a policy field of rolloutStrategy.nonBlockingClusters which would be a label selector/match expressions that indicates the labels on ManagedCluster objects that indicate if a cluster is a best effort cluster for this policy.
• Best effort means the policy will be enforced on the cluster but that if it stays noncompliant, it will not block the rollout from proceeding and it will not affect the overall status of the rollout. In technical terms, the cluster is treated normally but if it fails, the ManagedCluster object is checked to see if it’s a best effort cluster, if yes, it’s treated as a "Skipped" internally with the placement library. The root policy’s rollout status for that cluster would be "FailedNonBlocking".

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.