I think you've missed the point I was making. Essentially if you work back from the desired state of having IaC, CI/CD, test environments per MR, you likely se

I think you've missed the point I was making. Essentially if you work back from the desired state of having IaC, CI/CD, test environments per MR, you likely see something like k8s as a framework that helps you achieve that. Of course, if you start from "I just need a LAMP stack" you might have a very different conclusion. But when you reach the same endgame ( actually I need an environment for every MR ), you've probably incrementially built something more complex and bespoke. This will explain why there are dozens of us who are quite happy with the product. The only real question is, do you already know it and do you find it much harder to ship a deployment to a managed k8s cluster vs systemd unit files? If not, it might be an abstraction worth having. If you don't already know how though, then you might have better things to be doing with your time.