3 ms·
Idk what the author is referring to specifically but I can speak to my experience. I've been running a few single-node k8s clusters for a few years now. On GCP,
by bavell 3y ago
Idk what the author is referring to specifically but I can speak to my experience. I've been running a few single-node k8s clusters for a few years now. On GCP, the control plane fee is waived if you're running in a single region (no $70/mo fee). So basically you only pay for the VM itself.
As a solopreneur, I've saved so much time and money letting k8s run my workloads while I rack up billable hours and build products.
- jbnorth 3y agoWhy even use kubernetes then? You’d be better off just deploying the applications with docker compose on the host.
- mplewis 3y agoKubernetes makes it reasonably painless to wire up things like ingress and supports nice features such as operators.
- benterix 3y agoI'd argue ingress is even easier with Docker Compose. As for operators, it depends, but e.g. database operators are not really necessary on a single node cluster as you don't have discrepancies between nodes.
- smashed 3y agoI like the fact you qualified ingress as "reasonably" painless. Frankly it is not painless at all. Ingress is complicated and there is a ton of way to configure it, with all the forced tie in with the cloud provider's offering, be it l3 or l4 load balancing, various proxy services, etc. It's not easy at all either on docker-compose. You have to roll your own proxy container and take care of TLS termination, cert renewals, manage specific headers and config, etc. I am not sure what exactly I want to add to the conversation, only that either way, it's not "easy". I'd be glad to be proven wrong if you have a specific solution that makes ingress really painless.