News for hackers. Stuff that matters.

A comment on Don't use Kubernetes yet. Parent comment

Re:Don't use Kubernetes yet by mmcnl on Sunday June 19, 2022 @08:11AM (#31798578)
K8s is not about scaling, it's about declarative configuration management, which gives you the opportunity to easily scale as an added bonus. It feels extremely liberating to have my code and Kubernetes files in a repository, knowing that I can deploy this with one command to production on any Kubernetes cluster. It's a great infrastructure abstraction layer.

I agree it's expensive though. A docker-compose.yml on a VPS usually works fine as well. Requires some additional configuration outside the Docker ecosystem though.

[ Parent | on HN ]
Re:Don't use Kubernetes yet by icod on Sunday June 19, 2022 @09:28PM (#31805300)
what's wrong with git clone go build systemctl restart my-service

Why would I want to proxy through docker?

[ Parent | on HN ]
Re:Don't use Kubernetes yet by mmcnl on Monday June 20, 2022 @04:13AM (#31807607)
This question refers to the benefits of containerization and not Kubernetes. But to answer your question: your command is dependent on (1) the availability of Git, (2) Go and (3) systemd on your host OS. Without containers, this list of dependencies is dynamic and can change in size for every project. With containers, the list of dependencies reduces to one dependency only for every project: Docker.
[ Parent | on HN ]