←back to thread

1101 points codesmash | 1 comments | | HN request time: 0.222s | source
Show context
mrighele ◴[] No.45137889[source]
> If your Docker Compose workflow is overly complex, just convert it to Kubernetes YAML. We all use Kubernetes these days, so why even bother about this?

I find that kubernetes yaml are a lot more complex than docker compose. And while I do, no, not everybody uses kubernetes.

replies(3): >>45138013 #>>45138269 #>>45143229 #
esseph ◴[] No.45138013[source]
Having an LLM function as a translation layer from docker compose to k8s yaml works really well.

On another note, podman can generate k8s yaml for you, which is a nice touch and easy way to transition.

replies(4): >>45138153 #>>45138487 #>>45143983 #>>45146146 #
IHLayman ◴[] No.45138487[source]
You don’t need an LLM for this. Use `kubectl` to create a simple pod/service/deployment/ingress/etc, run `kubectl get -o yaml > foo.yaml` to bring it back to your machine in yaml format, then edit the `foo.yaml` file in your favorite editor, adding the things you need for your service, and removing the things you don’t, or things that are automatically generated.

As others have said, depending on an LLM for this is a disaster because you don’t engage your brain with the manifest, so you aren’t immediately or at least subconsciously aware of what is in that manifest, for good or for ill. This is how bad manifest configurations can drift into codebases and are persisted with cargo-cult coding.

[edit: edit]

replies(2): >>45139257 #>>45139426 #
1. hamdingers ◴[] No.45139257[source]
This assumes everyone who wants to run containers via podman has kubectl and a running cluster to create resources in which is a strange assumption.