> You're not doing that with the built-in tooling of e.g. Erlang/elixir either, because you're still missing all the other parts of your infrastructure. If you

> You're not doing that with the built-in tooling of e.g. Erlang/elixir either, because you're still missing all the other parts of your infrastructure. If you're deploying on managed serverless infrastructure, you can; certainly you want to manage the other parts of the infrastructure and co-ordinate changes (with terraform or similar), but you do it all at a higher level than what K8s offers you. And if you're deploying on an internal cloud or bare metal, I still find K8s is the wrong abstraction level (at least if your language offers a better deployment model than Linux VMs); probably you want to draw a boundary more similar to what serverless infrastructure providers do, and maintain everything "below the line" as part of your infrastructure rather than your applications. Yes, that means you've got to manage patching your OS and language runtime and rolling out those updates in a safe way, but you'll always need to update the "platform" at some point - even on K8s you end up having to spin up new clusters and shuffle apps from one to another - and drawing the boundary between the platform and the application at the place where it was traditionally done fits with the grain of the tools much better most of the time.