←back to thread

1101 points codesmash | 1 comments | | HN request time: 0.202s | 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 #
politelemon ◴[] No.45138153[source]
Use an LLM is not a solution. It's effectively telling you to switch your brain off and hope nothing goes wrong in the future. In reality things do go wrong and any conversation should be done with a good understanding of the system involved.
replies(3): >>45138230 #>>45138349 #>>45142425 #
1. SoftTalker ◴[] No.45138230[source]
When things go wrong, you just ask the LLM about that too. It's 2025.

/s