Has Anyone Else Faced This Silent Failure Issue with ArgoCD and Crossplane?

0
1
Asked By TechNinja42 On

I've been hitting my head against the wall with a frustrating issue between ArgoCD and Crossplane. Despite ArgoCD showing resources as "Healthy" and "Synced," Crossplane is actually failing to provision AWS resources - I mean, real problems with 400 errors popping up left and right. While ArgoCD gives a thumbs up, my Lambda functions aren't updating, RDS instances are stuck, and IAM roles are missing. I've searched high and low for information on this but found nothing. It seems like I'm the only one dealing with this silent failure where the health checks seem fundamentally broken. Is anyone else using health checks with Crossplane? Or are we all just turning a blind eye to ArgoCD's status? I managed to fix it by changing the order of condition checks, but I'm baffled that this isn't a common topic. Am I just super unlucky, or does this indicate a flaw in how many are using these tools?

4 Answers

Answered By CloudConfuser On

You might be misunderstanding how GitOps works. ArgoCD is just ensuring that the resources in your cluster match what’s declared - it’s not supposed to be a complete health monitor. If Crossplane is having issues, that’s actually on Crossplane to fix, not ArgoCD. You should set up proper monitoring tools to catch those errors instead!

SmartDev06 -

Exactly, ArgoCD isn’t a health dashboard. You need tools like Datadog or Grafana to really keep an eye on your infrastructure.

DessertDude -

Couldn’t agree more. Building out proper observability is key!

Answered By OldSchoolDev On

I had a similar dilemma a while back. Thankfully, I was aware of how ArgoCD health checks work before I tackled Crossplane. I bet many don’t realize they might need to implement custom health checks since the default ones can be misleading. People really should test and customize their setups!

DataWhizKid -

Yeah, the default checks can be pretty wonky. Testing is key!

TechNinja42 -

For sure, I'm learning that the hard way!

Answered By DevOpsGuru99 On

Glad you found a workaround! But honestly, Medium's subscription model kinda sucks. People are looking for accessible info, and not everyone can pay up. You should consider posting your findings straight to GitHub instead for better reach!

User1234 -

Totally agree! An open issue on GitHub would have way more visibility.

TechNinja42 -

I see what you're saying. I'll take it into consideration!

Answered By ConcernedDev On

Interesting that you opted for a Medium post instead of reporting a GitHub issue. It might be more effective for actual changes to happen. Maybe you should still consider that option?

TechNinja42 -

Yeah, it's a tough call. I want to make sure it gets the right attention!

CloudySkies -

The maintainers didn't see it as urgent, but I get it.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.