I've been battling what feels like a completely unique issue with ArgoCD and Crossplane—specifically, ArgoCD shows resources as healthy and synced, but Crossplane is failing to provision AWS resources. Despite receiving countless 400 errors from AWS, ArgoCD insists that everything is fine. I'm facing problems like Lambda functions that won't update, RDS instances stuck, and IAM roles that aren't being created, all while the ArgoCD dashboard rides high with false confidence. I've searched high and low for answers online, and I'm coming up empty-handed. Has anyone else experienced this issue? Is ArgoCD's health check logic just faulty, or am I missing the bigger picture? I managed to fix the issue by reordering the condition checks, but I'm baffled that no one else seems to have noticed this problem. Please tell me I'm not alone!
5 Answers
I think the best next step is posting on GitHub instead of Medium. You could raise awareness for an issue that might affect a lot of users who are unaware of it.
That's understandable, but there’s definitely a need for support on this front.
Honestly, I think there's a bit of confusion here. ArgoCD operates under the premise that the resources are synced based on the state files; that's why it shows as healthy. The subsequent failure by Crossplane is a different issue but doesn't negate the fact that the sync state is correct. GitOps is more about matching the desired state than it is about ensuring every deployment is in perfect health.
True, ArgoCD won’t catch every dependency failure. It just offers a way to keep resources in sync.
Exactly! For real monitoring, you need tools like Grafana or Datadog.
This sounds like a major misstep in condition checks. If 'Ready' doesn't accurately reflect resource health, then reworking the check should be a priority for them. Instead of merely altering the reporting, pushing for a bug fix would be more beneficial.
I've dealt with this before! I figured out the health check behavior of ArgoCD in advance, which made it easier to avoid these pitfalls. It feels like people should definitely be testing more and writing custom health checks if the defaults don’t meet their needs.
Yeah, this should be more widely known among users!
Absolutely! I think more tutorials or documentation would help newcomers.
Great job finding a workaround! Just a heads-up, though—be mindful about posting on Medium. A lot of folks aren't fans of their member-only content.
Yeah, seriously. Member-only stories are a turn-off for many.
I totally agree. It's discouraging to see good content hidden behind a paywall.
I've actually talked to some maintainers about it. They see it as more of a community issue rather than a pressing bug.