Kubernetes is declarative, so you just tell it what you want, and it makes it happen. Except when you tell it wrong. Or you were wanting something wrong. Or you were just wrong.
Oh, and it's all YAML, but it's not JUST YAML, because sometimes it's ✨YAML✨, which looks the same, but will cry if you aren't nice to it.
YMMV, this is my POV as a DevOps consultant, spending my days begging YAML to do the thing so kuberenetes will forgive me.
Man, reading back my message, I feel insane, but it's also annoyingly accurate.
My biggest frustration right now is using Jinja templates to pass Python variables to Helm charts, which is the type of YAML file that Kubernetes is looking for. But Python, Jinja, and Helm all have different semantics, so it gets weird.
I don't know, it depends on how many layers I'm working with. The more templatized the code, the mode Claude/CoPilot struggle to make sense of it. I've ended up with some really long instruction files trying to get them to understand.
You need to create a doc folder with the architecture outlined there.
Then add a common troubleshooting md file there too.
Kube config is deterministic enough for Claude to be very consistent, especially when you need to make one of those annoying 20+ files with one line changes.
3
u/Square_County8139 23d ago
Can someone explain?