-
Story
-
Resolution: Unresolved
-
Medium
-
False
-
-
False
-
-
-
Argo Sprint 1
Work on upstream issue
https://github.com/argoproj/argo-cd/issues/19547
Summary
Clusters/namespaces which are managed by a certain argocd server will (optionally) contain info regarding the server which manages them.
Motivation
A few days ago I needed to troubleshoot some problem I had in a certain namespace which is managed by an argocd instance which exist in a different cluster. Since I have multiple argocd instances, each responsible for different clusters, I tried to find info inside the cluster regarding which argocd instance is responsible for it. Unfortunately, I didn't find any references inside my target cluster.
Proposal
I suggest to add an optional flag which if is enabled will cause the argocd instance to inject some configmap/labels or other way of pointing to the argocd server which manages the relevant resource(s).
- clones
-
OEIIITB-17 [gitops-docs-1.12] Issue in file argocd_instance/argo-cd-cr-component-properties.adoc
- Closed
- is cloned by
-
OEIIITB-20 [Notifications] Make GH Check Runs part of ArgoCD Notifications natively
- In Progress