3 ms·

ugh it's great that k3s exists, but frustrating that kube can't hit this target on its own it seems like small clusters are not economical with vanilla kube. (

ugh it's great that k3s exists, but frustrating that kube can't hit this target on its own it seems like small clusters are not economical with vanilla kube. (I say this having frequently tried and failed to do this, but not having done napkin math on system pod budgets to prove it to myself generally). and this gets worse once you try to install any kind of plugins or monitoring tools. I really wonder if there's a hole in the market for 'manage 5-10 containers with ingress on one or two smallish nodes'. Or if there's a hard core of users of alternatives like swarm mode. this guy https://mrkaran.dev/posts/home-server-nomad/ https://mrkaran.dev/posts/home-server-nomad/ evolved his home lab from kube to nomad to terraformed pure docker over 3 years.

runlevel1 5y ago
It'd be a whole lot easier to hit this goal without needing a minimum of 3 nodes for Etcd quorum. I'd love to see K8s get K3s' support for using an external MySQL, Postgres, or SQLite instead of Etcd.
- awinter-py 5y ago
  from this https://github.com/k3s-io/kine https://github.com/k3s-io/kine it seems like k3s was born out of a rancher labs project called 'kine' that does what you're describing?
outworlder 5y ago
> it seems like small clusters are not economical with vanilla kube Why, though? The memory footprint is a couple hundred MB. You do need ideally 3 nodes but you _can_ run in one. I have deployed a single-node MicroK8s without issues. Usually, the containers themselves (your workloads) are the hogs. Deploying multiple pod replicas in a single machine has innate inefficiencies.
gizdan 5y ago
Majority of people using K8s aren't hobbyists. They're enterprising running hundreds if not thousands of nodes. For most of them the offering of K3s is irrelevant. They can spare that extra few hundred megs of RAM needed.
- awinter-py 5y ago
  as the former parent of a 100+ node cluster, am mostly with you -- but we also had dev environments that were 1-10 pods, and where we would have liked low-overhead and didn't need HA also valuable for creating local copies of cloud infra so you can develop + test

runlevel1 5y ago

It'd be a whole lot easier to hit this goal without needing a minimum of 3 nodes for Etcd quorum. I'd love to see K8s get K3s' support for using an external MySQL, Postgres, or SQLite instead of Etcd.

awinter-py 5y ago
from this https://github.com/k3s-io/kine https://github.com/k3s-io/kine it seems like k3s was born out of a rancher labs project called 'kine' that does what you're describing?

outworlder 5y ago

> it seems like small clusters are not economical with vanilla kube Why, though? The memory footprint is a couple hundred MB. You do need ideally 3 nodes but you _can_ run in one. I have deployed a single-node MicroK8s without issues. Usually, the containers themselves (your workloads) are the hogs. Deploying multiple pod replicas in a single machine has innate inefficiencies.

gizdan 5y ago

Majority of people using K8s aren't hobbyists. They're enterprising running hundreds if not thousands of nodes. For most of them the offering of K3s is irrelevant. They can spare that extra few hundred megs of RAM needed.

awinter-py 5y ago
as the former parent of a 100+ node cluster, am mostly with you -- but we also had dev environments that were 1-10 pods, and where we would have liked low-overhead and didn't need HA also valuable for creating local copies of cloud infra so you can develop + test