I'm really at my wit's end here. I've been debugging what I can't help but call the most annoying GitOps issue I've ever encountered. So here's the deal: ArgoCD is showing all my resources as "Healthy" and "Synced," but Crossplane is actually failing to provision AWS resources! I'm getting a lot of 400 errors from AWS, but ArgoCD is acting like everything is just peachy. It's frustrating to see Lambda functions not updating, RDS instances stuck, and IAM roles not created—all while ArgoCD's dashboard continues to falsely reassure us that everything's fine.
I've tried Googling this issue like crazy, but I can't find anyone else reporting similar problems. It feels like I'm in a parallel universe where I'm the only one using ArgoCD with Crossplane and experiencing these broken health checks. The Lua logic for health checks processes the status conditions in array order, which is the root of the problem—I had to reorder the checks myself to highlight errors first.
So, my questions are:
* Is everyone just not using health checks with Crossplane?
* Are you all simply watching AWS directly and ignoring ArgoCD?
* Am I just the unluckiest person in the world?
* Did I somehow end up with a weird configuration that no one else has? Please tell me I'm not alone!
2 Answers
Honestly, I'd recommend opening a GitHub issue instead of relying on Medium. You might be surprised at the feedback or support you could get from the community that way.
Hey, I completely get your frustration! I think it’s great you found a workaround. But honestly, Medium can be pretty inaccessible with that member-only content. Just a suggestion, you might want to consider sharing it in a more open forum.
100% agree, Medium can be quite a pain.
I avoid it too; can’t deal with member-only barriers.
I chatted with some maintainers, and they mentioned this isn't a big priority for them. It sounds like they feel it’s more of a community challenge.