Epic Goal

• The goal of this epic is to consider to make specifying the sidecar image for the plugin optional. When the image is not specified the operator would just use the product image being used for the repo server.
• The benefit to the customer is currently the operator requires specifying an image when using the sidecar plugin which requires the customer to have to create maintain a custom image. In many cases the customer just needs the tools that are already included in the Argo image being used (i.e. kustomize and helm) and at the same version
• The command "oc explain argocd.spec.repo.sidecarContainers.image" shows the image as optional however this appears to be inherited description and is incorrect.
• While the customer can leverage the product image now, it is additional effort keeping the image specified aligned with the current product image.

Why is this important?

• Simplifies migrating from legacy CMP to the sidecar CMP since it additional friction for customers in terms if creating and maintaining a sidecar image

Scenarios

1. Customer migrates from legacy CMP to a sidecar CMP and doesn't want to have to maintain a custom issue.
2. Customers crteates a new sidecar CMP but only requires kustomize/helm and doesn't want to create and maintain a custom image.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• When image is not specified operator automatically uses product image

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. Do we want to support the usage of the product image for this scenario (full or comercially reasonable?)

1. Downside of supporting this use case is it may limit our flexibility in maintaining the image, i.e. customers opening support cases complaining we removed tool x or y from the image. Also could lead to image bloat as customers ask for additional tools to be included.

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