I'm seriously frustrated right now after spending a week grappling with an issue that seems completely insane. ArgoCD shows my resources as "Healthy" and "Synced" while Crossplane is failing to provision AWS resources, resulting in all sorts of 400 errors! It's surreal since my dashboard says everything is fine, but in reality, Lambda functions aren't updating, RDS instances are stuck, and IAM roles aren't being created at all.
I've Googled this extensively, and there's virtually no information about it — no blog posts, Stack Overflow threads, or GitHub issues discussing this situation. It feels like I'm the only one who has encountered this breakdown in health checks.
The crux of the problem seems to be in the Lua logic for the health checks; if `Ready: True` appears before `Synced: False` in the checks, ArgoCD just deems everything okay, ignoring that the cloud resources are failing.
I managed to fix the issue by reordering the checks, but I'm baffled as to why no one seems to know about this problem! Are people just skipping health checks with Crossplane? Is everyone else directly monitoring AWS and disregarding ArgoCD's status? Am I going mad or did I stumble upon some uncommon configuration? It can't just be me, right?
I even wrote a detailed technical article and opened a GitHub issue to hopefully get this fixed down the line.
1 Answer
It's great you found a workaround! But posting it on Medium as a 'Member-only story' isn’t ideal. It would be better to share it where more people can access it easily.
Exactly, Member-only stuff just limits who can see your info. Why not just keep it open for everyone?