upvote
I think his argument is that the functionality is unnecessary. You don’t need dynamic service scaling because your single-instance service has such high capacity to begin with.

I guess it’s all about knowing when to re-engineer the solution for scale. And the answer is rarely ”up front”.

reply
Dynamic scaling is not really even available on a single node kubernetes.

I was thinking more of

Running multiple websites. i.e. 1 application per namespace. Tooling i.e. k9s for looking at logs etc. Upgrading applications etc.

reply
Namespaces exist in Linux [0], they weren’t invented by K8s.

You can view application logs with anything that can read a text file, or journalctl if your distro is using that.

There are many methods of performing application upgrades with minimal downtime.

0: https://www.man7.org/linux/man-pages/man7/namespaces.7.html

reply