Repository navigation
Replies: 1 comment 1 reply
|
Hi @lstyles, do you have any resource limits on your application controller workload? Also, 450 resources for a given app is not a small amount of resources, and I'd really suggest that you think about cutting your applications in more slices. E.g. you wrote that you have 40 microservices per application. I think the best practice here would be to cut each microservice into its own application. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm at a bit of a loss as we're experiencing some syncing issues in (fortunately) our non-production cluster.
We have 3 applications with ~40 microservices (deployment + service) and few ingress resources. The total of resources (I'm assuming) watched by ArgoCD is ~450 per application. (Counted by applying filter and seeing how many hidden resources it thinks it has).
I am able to manually Sync by selecting
Apply Out of Sync Only. Automated sync always ends up in application controller restarting.I've increased the repo server timeout to 180s and resources on the controller pod.
but I'm not even seeing a lot of activity on the repo server.
We're now deploying any helm charts or kustomize manifests. Just plain YAML resources.
When a full sync is triggered, I get the following few log lines:
the last log line is repeated a few times and each contains long list of resources. Then the controller pod restarts.
Any suggestions where to look next please?
All reactions