-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
2
-
False
-
None
-
False
-
Before this update, user were not able to set custom image for applicationset controller even after setting it in argocd CR. After this update, users configuration will be respected and users will be able to set customer applicationset controller image.
-
-
-
GitOps Crimson - Sprint 3262
Description of problem:
Operator supports overriding default image for Argo CD components(server, repo-server, application-controller, applicationset-controller, notifications-controller) using .spec.image & .spec.version fields in ArgoCD CR. However, the applicationset-controller deployment doesn't respect this configuration. The image value is not reflected in the deployment.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
Create ArgoCD CR
apiVersion: argoproj.io/v1beta1kind: ArgoCDmetadata: name: examplespec: image: quay.io/argoproj/argocdversion: v2.12.0applicationSet: enabled: true
Actual results:
The image in applicationset-controller deployment point to default value set by the operator.
Expected results:
The applicationset-controller deployment should use image specified in .spec.image & .spec.version fields from ArgoCD CR.
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
ApplicationSet controller image can be configured using .spec.applicationSet.image & .spec.applicationSet.version fields of the ArgoCD CR. I believe, the operator should proritize the image configuration in following order
default value < .spec.image < .spec.applicationSet.image
*
- links to
-
RHEA-2024:139495 Errata Advisory for OpenShift GitOps v1.15.0