[SOLAR_FIELDS]

Great if you’re you, but try getting AverageSWE a local kube setup and see how quickly they ramp up on it

In my ideal world everyone would use kubernetes, it is the hammer and everything is a nail, but we must recognize that it is difficult for a lot of people to pick up.

That being said, if you’re deploying on kube in production, use kube locally. But if you’re not, dont

[osigurdson]

Using kube in production but really, even if I wasn't, I would still use the podman play kube approach. It isn't hard (at all) and isn't kubernetes, just kubernetes yaml. I actually find docker / compose a bit harder sometimes with the daemon running in the background.

[sandGorgon]

this is OpenClaw's docker compose yml - https://github.com/openclaw/openclaw/blob/main/docker-compos...

I'm not arguing for the relative superiority of jsonnet vs yaml vs anything else. I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default.

I'm just making it possible to run those on kubernetes seamlessly.

[SOLAR_FIELDS]

I mean if you are going to bother to introduce the concept of kubernetes yaml to a developer shouldn’t you just go all the way and teach them proper k8s instead of some weird intermediary? I fail to see the value of offering k8s yaml that isn’t k8s or one of its siblings that’s basically k8s