-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Argo-cd fails on service monitor synchronization (and other resources) #1884
Comments
I logged also a related issue with the same strange behaviour: #1887 |
When I attempt to create this locally, I get this error:
|
Have you installed the CRD please? |
Yes, it's running on the cluster where Prometheus is installed, so all necessary CRDs are in place. Is there any way to get information on why kubectl failed? Or maybe get the exact manifest of what exactly is executed with kubectl? |
we've noted that CRDs can take a few moments to install. Perhaps related. |
Describe the bug
Argo-cd sometimes fails to do synchronization for the whole application. I managed to narrow that to some specific kinds of resources like ServiceMonitor (for Prometheus Operator).
What's more interesting, I can synchronize these resources when I sync them manually one-by-one, but sync for all resources (or subset of resources) fails.
To Reproduce
Expected behavior
Sync everything successfully or at least provide a clear reason why sync has failed.
Version
v1.0.2
Logs
Have you thought about contributing a fix yourself?
I probably can do a little more troubleshooting but I need some info on how to enable some more verbose output to narrow down the issue.
The text was updated successfully, but these errors were encountered: