[bongobingo1]

I think this can replace docker-compose in deployment - if thats how you deploy and are willing to alter your workflow slightly.

I've done this for a while on small or disconnected systems, systemd + podman is very nice, the regular unit file generators are very usable + modifiable.

From the development side, the issue is unit files must be "installed", I can't just have a set of `x.service y.service" files and `systemd start $(pwd)/x.service`, so the overhead is a bit awkward there.

`podman play kubelet` is sort of there, except it doesn't support some networking options in the kubelet file, so its not a complete replacement.

Podman also includes support for running kubelet files via systemd but I don't use that myself.

I think ideally kubelet files with some extra podman annotations are the compose replacement, even if writing them isn't as pleasant as compose files. They you could `podman play kube x` to boot the dev stack and use the systemd-x-kubelet template to deploy.

[INTPenis]

>I think ideally kubelet files with some extra podman annotations are the compose replacement, even if writing them isn't as pleasant as compose files.

People have been telling me this for years now and I have yet to see a working example.

[bongobingo1]

Yes, what I mean is, ideally kubelet files + podman would be a sufficient replacement. Not drop-in, but close enough, but it's not there ergonomically (yet?).