-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
GITOPS Sprint 233, GITOPS Sprint 234, GITOPS Sprint 235, GITOPS Sprint 238, GITOPS Sprint 239, GITOPS Core Sprint 3248, GITOPS Core Sprint 3250, GITOPS Core Sprint 3251, GITOPS Core Sprint 3252, GITOPS Core Sprint 3253, GITOPS Core Sprint 3254, GitOps Tangerine - Sprint 2255, GitOps Tangerine - Sprint 3256, GitOps Tangerine - Sprint 3258
Description of problem:
when we label more than 100 namespace as "managed-by=argo" so that those namespaces would be synced by argo, argocd fails to do tasks such as sync or refresh. argo cd controller pod has logs which i think they are related with this issue(please see the attachment).
https://access.redhat.com/support/cases/#/case/03444348
replicates https://access.redhat.com/support/cases/#/case/03462000
https://redhat-internal.slack.com/archives/CMP95ST2N/p1669039864256719
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
label more than 100 namespace as "managed-by=argo" so that those namespaces would be synced by argo
Actual results:
argocd fails to do tasks such as sync or refresh.
Expected results:
argocd should sync or refresh.
Reproducibility (Always/Intermittent/Only Once):
Build Details:
Additional info (Such as Logs, Screenshots, etc):
- is related to
-
GITOPS-2807 Investigate solutions for managing too namepaces by namespace scope instance
- Closed
-
GITOPS-3713 Analyze resource usage in a typical Cluster scoped ArgoCD instance based setup
- Closed
- links to