Closed jaydipdave closed 8 months ago
looks like a problem with JSON marshaling - anyone running OpenShift able to help?
I was debugging the issue with OpenShift.
My findings below:
This could be the case with many OpenShift or Kubernetes clusters, specially in Financial institutions.
Do we really need to fetch all the resources of all the resource types at the time of synchronization of an application? Can't we limit it to the namespaces mentioned in the project?
I also tried narrowing down the "argocd-manager" role permissions to a specific namespace. The response is faster, but that doesn't work.
The TImeout happens here: https://github.com/argoproj/argo-cd/blob/master/controller/cache/cluster.go#L320
Duplicate of #2176
Argo CD does not use pagination during initial cluster state fetching. This could potentially cause a timeout error. The pagination was introduced in https://github.com/argoproj/argo-cd/pull/3299 .
The change is is available in https://github.com/argoproj/argo-cd/releases/tag/v1.5.0-rc3 . Please give it a try.
Describe the bug Deployment on EKS and GKE works great. We have to deploy applications on OpenShift as well. OpenShi[f]t version:
Added the OpenShift cluster using :
argocd cluster add --kubeconfig=/Users/xxxxxx/.kube/openshift1 --insecure "openshift"
Created the application and saved it successfully:
I checked the "argocd-manager" service account and related clusterrole / clusterrolebindings. They are created properly in kube-system namespace. I can also access the openshift using that service account.
Version
Logs
argocd-repo
argocd-server