Epic Goal

The goal is to support Argo CD's "core" mode for low-footprint installations where the Argo CD API server is not installed/running.

The "core" mode is implemented mainly in the Argo CD CLI, which uses Kubernetes-native mechanisms to emulate what the Argo CD API would do.

For this, users need access to a productized version of the Argo CD CLI that is easily installable as RPM. We also need to support CLI use cases.

Why is this important?

This Epic is part of bringing GitOps to Microshift, which is a RHDP priority.

Also, lots of our users revert to the upstream version of the CLI to implement their use cases (e.g. automation in CI pipelines), which poses an unnecessary risk to them and also puts them in kind of a "blind spot" when it comes to support (because we do not officially support the CLI).

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• For each release of OpenShift GitOps, an appropriate RPM is produced and published that contains the argocd binary.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. ...

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment