Epic Goal

There is a problem using annotation-based resources tracking (see here) in the case of multiple ArgoCD instances. When multiple ArgoCD instances have Applications with same name, it is impossible to differentiate their resources and Applications are in the infinite sync loop. ArgoCD already supports this scenario, but only with legacy label-base resource tracking (using application.instanceLabelKey). The goal is to enable this scenario with annotation-based tracking.

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Argo CD support annotation-based resource tracking with multiple Argo CD instances when Applications have the same name

Dependencies (internal and external)

TBD

Previous Work (Optional):

TBD

Open questions::

TBD

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