< High-Level description of the feature ie: Executive Summary >

Goals

Add init container support for Argo CD server and controller. This includes updating the Argo CD CRD with the new field called initContainers in the controllerSpec and serverSpec.

  *

• • (Optional) Use Cases

Allows users to add any additional configuration through the sidecar containers.

Out of scope

Anything beyond initContainers

Dependencies

NA

Background, and strategic fit

A few customers have requested for the support to add sidecar containers to the controller and server, similar to how they can do it today with repo server.

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Acceptance Criteria (Mandatory)

• Argo CD CRD is updated with the new fields to support SideCar and InitContainers for Application Controller and Server in the Argo CD Operator
• Propogate the changes to the GitOps Operator
• Add required tests
• Build and tested in the Downstream
• Update Documentation

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation Considerations

• Documentation to upstream operator

  What does success look like?

Users can add sidecar containers to controller and server.

Impact

NA

Related Architecture/Technical Documents

<links>

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