I'm at my wit's end here! I've spent nearly a week trying to debug a frustrating issue with ArgoCD and Crossplane. Despite ArgoCD showing resources as 'Healthy' and 'Synced,' Crossplane just isn't provisioning AWS resources properly, throwing constant 400 errors. It's infuriating because things like Lambda functions and RDS instances are failing to update, yet ArgoCD acts like everything is perfectly fine. It's hard to believe nobody else is facing this, as I've found zero information online about this specific problem. I've managed to fix it by reordering the health checks, prioritizing error conditions over healthy ones. I just can't shake the feeling that I'm missing something or that everyone else is just monitoring AWS manually. Am I really the only one who's hit this?
4 Answers
Look, I think there’s a fundamental misunderstanding here. The resources are indeed synced. ArgoCD is doing what it's meant to, which is ensuring that your cluster matches the expected state. If Crossplane fails later on, that’s separate from what ArgoCD is reporting. You need to have proper monitoring in place for the health beyond what ArgoCD offers.
Thanks for sharing your experience! We're considering migrating to the same stack, and your write-up might save us tons of trouble. Have you thought about posting a GitHub issue on this? It seems like it could be useful for more people.
Been there, done that! I faced this issue years ago. Most folks using Argo should be aware of how to write custom health checks. It’s critical because Argo won't always detect misconfigurations unless you set it up right.
Glad to hear you found a workaround! But honestly, I can't believe you'd post it on Medium behind a paywall. It should really be a GitHub issue instead.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures