Value Statement

When enabling cluster-lifecycle on ARO-HCP, we will only apply the clusterlifecycle-state-metrics deployment during runtime and exclude any unnecessary components such as cluster-curator, clusterclaim, and provide-credential. By excluding those resources, we can reduce resource overhead and simplify the deployment for ARO-HCP environments.

Note: Rewrite this story to focus more on the automation flow during compile time.

Definition of Done for Engineering Story Owner (Checklist)

• [] The clusterlifecycle-state-metrics deployment is successfully deployed on ARO-HCP when cluster-lifecycle is enabled through MCE.
• [] The cluster-curator, clusterclaim, and provider-credential components are excluded from the deployment on ARO-HCP.

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 template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

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