I'm really struggling with an ArgoCD and Crossplane issue that seems to have no online discussion. I've spent a week troubleshooting a bizarre situation where ArgoCD indicates that my resources are 'Healthy' and 'Synced' even when Crossplane is failing to provision AWS resources. Issues like Lambda functions not updating and IAM roles not creating have been a nightmare, yet ArgoCD displays everything as fine. I suspect it's related to the way ArgoCD processes status conditions in an array, which overlooks crucial failure signals. I'm curious if anyone else has faced this, or if people are just ignoring ArgoCD's status altogether. Did I just publish a unique bug that's not widely known?
3 Answers
Man, I've run into this before! I was aware of Argo's health check behavior before working with Crossplane, so I dodged a lot of headaches. Seems like a lot of folks aren't testing custom health checks as they should when using ArgoCD.
It's great that you found a workaround! But I have to say, Medium articles can be a bit of a hassle when they're behind a paywall. Maybe consider sharing this as an open-source issue instead?
Totally agree! A GitHub issue would help reach more people who could be affected.
I get where you're coming from, but keep in mind that ArgoCD is primarily about syncing the state of the resources, not necessarily monitoring their health continuously. Crossplane's errors won't always reflect in ArgoCD's interface. It's more about how GitOps works, ensuring what’s in your cluster matches your declared state.
You really should supplement ArgoCD with a proper monitoring tool like Datadog or Prometheus for better insight.
Yeah, I think a lot of folks misunderstand this. ArgoCD won't show everything wrong unless it's a sync issue.
Exactly! I avoid Medium if it's not free.