Value Statement

In OCM-io upstream, we have native support for an applifecycle addon install using the clusteradm CLI that is currently based on AppSub. Qiu Jian wants us to rework the addon so it's more easily maintainable by shifting away from embedded manifests in favor of a Helm chart.

The best path forward is to change the app addon in upstream to use the Argo CD Pull Model integration.

This approach aligns with our plan to deprecate AppSub in upstream. Reducing maintenance for the workload management team and also satisfies Qiu Jian’s requirement to bring the app addon up to date. This also helps make writing e2e for Argo CD pull integration easier because it's now installable via clusteradm CLI.

Definition of Done for Engineering Story Owner (Checklist)

• upstream clusteradm CLI is able to install argo cd pull integration addon
• remove appsub addon from clusteradm CLI

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.