4 ms·

What clicks me about Kubernetes is not about orchestration or zero downtime or scaling,... I can just use Kubernetes on 1 node for all of my services. What mat

What clicks me about Kubernetes is not about orchestration or zero downtime or scaling,... I can just use Kubernetes on 1 node for all of my services. What matters is the declarative approach of Kubernetes. It's like the first time I learnt about React: declarative renderering/deployment based on state !

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 ago
  Try 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 ago
    Can 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 ago
      Yes, you can easily join multi master nodes or worker nodes with k3s.
      - heavyset_go 6y ago
        Awesome, thanks.
- arcticfox 6y ago
  As 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 ago
    Go is the new Java it seems :)
astrange 6y ago
Didn't Ansible/Puppet/Salt/Chef already do this? I don't even know what Kubernetes is (because I refuse to look it up) but somehow all these people have heard of it and apparently not any of the previous simpler solutions.
- revskill 6y ago
  Not quite. With kubernetes, you have the only choice, it's declarative yml. With Ansible, you can easily shoot yourself in the foot with imperative shell command. The point is, Kubernetes is very opinionated (for good reason) on how it's hard for you to break your system.
- lmm 6y ago
  Puppet does 80% of what Kubernetes does, but you have to manually distribute your services across your hosts, and if you want failover or autoscaling then you have to implement them yourself. Imagine Puppet but instead of saying "run service X and Y on host A, run service Z and W and the hot spare for U on host B, ...", you just say "deploy at least 3 instances of service X with this much CPU/memory, deploy at least 2 instance of service Y with at least this memory, these are the hosts you have available, you figure it out".

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 ago
Try 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 ago
  Can 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 ago
    Yes, you can easily join multi master nodes or worker nodes with k3s.
    - heavyset_go 6y ago
      Awesome, thanks.
arcticfox 6y ago
As 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 ago
  Go is the new Java it seems :)

astrange 6y ago

Didn't Ansible/Puppet/Salt/Chef already do this? I don't even know what Kubernetes is (because I refuse to look it up) but somehow all these people have heard of it and apparently not any of the previous simpler solutions.

revskill 6y ago
Not quite. With kubernetes, you have the only choice, it's declarative yml. With Ansible, you can easily shoot yourself in the foot with imperative shell command. The point is, Kubernetes is very opinionated (for good reason) on how it's hard for you to break your system.
lmm 6y ago
Puppet does 80% of what Kubernetes does, but you have to manually distribute your services across your hosts, and if you want failover or autoscaling then you have to implement them yourself. Imagine Puppet but instead of saying "run service X and Y on host A, run service Z and W and the hot spare for U on host B, ...", you just say "deploy at least 3 instances of service X with this much CPU/memory, deploy at least 2 instance of service Y with at least this memory, these are the hosts you have available, you figure it out".