Feature Overview

Add support for sidecars to argocd-server and application-controller to the operator. This has come from a customer RFE and implementing it will allow more customers to migrate their existing applications to use GitOps. 

Goals

• Customers have more flexibility in how they arrange their containers
• Adding support for sidecars to the API server and application controller like there already is in the repo server allows folks to utilize things like proxies in other areas of Argo CD

Requirements

Use Cases

Support case 03716751 - Barclays:

• “Our argocd server and controller components require a proxy sidecar container for managing a DMZ environment”

Out of scope

Changes in the upstream, this is an operator-only change.

Dependencies

None known.

Background, and strategic fit

This Jira is part of SECFLOWOTL-6 as it can allow folks already using GitOps to bring more of their applications over to a gitops workflow. It may also unblock some legacy applications that require specific setups, like org-level requirements around proxies, to migrate to GitOps.

Assumptions

None known.

Customer Considerations

None known.

Documentation/QE Considerations

• Will need docs additions:
• Release notes mention of the new field available in the ArgoCD CR
• Docs update to the CR properties page (should mention the sidecar container attribute that is already available on the repo server as well as the new attributes available for the api server and the application controller) https://docs.openshift.com/gitops/1.10/argocd_instance/argo-cd-cr-component-properties.html#argo-cd-properties_argo-cd-cr-component-properties 

Impact

As this is an operator-only change, we don't need to wait on an upstream proposal to implement it. This should be able to be worked on in parallel to any ongoing upstream work.

Related Architecture/Technical Documents

Definition of Ready

• The objectives of the feature are clearly defined and aligned with the business strategy.
• All feature requirements have been clearly defined by Product Owners.
• The feature has been broken down into epics.
• The feature has been stack ranked.
• Definition of the business outcome is in the Outcome Jira (which must have a parent Jira).