4 ms·
Here's the thing that gets me: Docker Compose and Docker Swarm can offer declarative infrastructure and only take up under 50MB of resident memory. I need 2GB
by heavyset_go 6y ago
Here's the thing that gets me: Docker Compose and Docker Swarm can offer declarative infrastructure and only take up under 50MB of resident memory.
I need 2GB minimum for a K8s master node, 2GB minimum for monitoring, and then 700MB minimum for each worker node[1].
I just can't justify running K8s for a blog when there are less expensive and complex offerings out there.
[1] https://docs.kublr.com/installation/hardware-recommendation/ https://docs.kublr.com/installation/hardware-recommendation/
- turtlebits 6y agoTry K3s. I run it on 3x of OVH's cheapest VPS ($3.50/mo) and works great. I have Postgres, Hasura, Keycloak, Riemann, Riemann dashboard and Digdag running- the cluster has been up over a year with no issues.
- heavyset_go 6y agoCan I use multiple machines as nodes for K3s? I think the last time I looked at it, clusters were limited to one machine, but that was a long time ago.
- revskill 6y agoYes, you can easily join multi master nodes or worker nodes with k3s.
- heavyset_go 6y agoAwesome, thanks.
- arcticfox 6y agoAs a big K8s fan, I have no idea why it's so fat. I'm sure there's a reason, but I really don't know where the bloat comes from. I just run K*3*s when I'm not using a managed cluster, and it works great and is lightweight. I've never noticed whatever is missing from it.
- pas 6y agoGo is the new Java it seems :)