Epic Goal

• Enable users to deploy their own or third party UI extensions for Argo CD using the operator.
• This would require the Server component to support init containers and/or mounting volumes similar to the way it is currently supported for the Repo server.

Why is this important?

• There are a number of extensions for Argo CD, for example Rollouts, that enhance the user experience. It's also not uncommon for organizations to develop their own extension to enhance some aspect of the Argo CD experience based on their own requirements
• Another extension is the metrics extension (https://github.com/argoproj-labs/argocd-extension-metrics)
• Note there is an existing issue to support the Rollouts Extension (GITOPS-3604)

Scenarios

1. Organization wishes to deploy an existing third party extension (Rollouts, Metrics, etc)
2. Organization develops their own extension and wants to deploy it in OpenShift GitOps

Acceptance Criteria (Mandatory)

• 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

• 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