Epic Goal

• The goal of this epic is to make Image Updater configuration available in the target external cluster.

Why is this important?

• In pre-v1.0 (annotation based) Image Updater, multi-cluster application image updater worked seamlessly. With the CRD based Imager Updater, the CRD does not live in the remote cluster when the application is deployed. It is important to reinstate this feature in the new CRD based Image Updater.

Scenarios

1. We run ArgoCD in a management cluster with workloads deployed to ~30 target clusters. We use ApplicationSets extensively (~300+) to template Applications across environments, regions, and clusters.

Other Considerations

• https://github.com/argoproj-labs/argocd-image-updater/issues/1382
• https://github.com/argoproj-labs/argocd-image-updater/discussions/1350

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.