Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

K3s – Lightweight Kubernetes

k3s.io

Post reply on HN
Print view View original

21–30 of 194 posts

Re: K3s – Lightweight Kubernetes

#21

Post by djsumdog »

rhizome31 wrote: post #8
redmorphium wrote: post #5

Earlier quoted context omitted.

No, for the same reason that Martin Fowler argues you should start with a monolith first before moving to a microservices architecture.

What is currently a good alternative for a small business who needs to distribute containers on a handful of nodes? Docker swarm mode?

A single baremetal server with just docker containers. It's much easier to migrate from just containers running on nodes to an orchestration system (marathon, nomad OR k3s/k8s; there are other options) than to start with the orchestration system.

Re: K3s – Lightweight Kubernetes

#22

Post by zoobab »

Welcome to 2019 where an "embedded" system has 1GB RAM.

The problem of GO is that all those unused libraries are loaded in RAM instead of staying on disk, and loaded when needed.

An helloworld in GO (around 1.6MB) is still too large for my openwrt router.

Re: K3s – Lightweight Kubernetes

#23

Post by ithkuil »

zoobab wrote: post #22

Welcome to 2019 where an "embedded" system has 1GB RAM. The problem of GO is that all those unused libraries are loaded in RAM instead of staying on disk, and loaded when needed. An helloworld in GO (around 1.6MB) is still too large for my openwrt router.

Like every process, the text segment is demand paged so it doesn't consume ram unless it's actually needed. What you probably mean is that multiple copies of the same library cannot share the same physical memory pages.

Re: K3s – Lightweight Kubernetes

#24

Post by comboy »

sliken wrote: post #16
comboy wrote: post #10

Not trying to be snarky, just a sincere question - why would you use kubernetes for something like IoT?

Because I want my doors, windows, garage door, smoke alarms, security system, and any other smart thing in my house even when the IoT controller dies. I also want as much functionality as possible if my ISP (Comcast) decides on another "maintenance" window. So that basically means local smarts and fall over in the case of a hardware failure.

Same. What does it have to do with kubernetes?

Re: K3s – Lightweight Kubernetes

#25

Post by sandGorgon »

Oh nice - this is by the Rancher guys. Would love to compare this not with k8s, but with Docker Swarm.

Docker Swarm on Raspberry Pi is a very common thing. So, from a performance perspective, these are on par.

Another question is around ingress and network plugin - is it a seamless "batteries included" experience ? Because these are two of the biggest pains in k8s to decide and setup .

Re: K3s – Lightweight Kubernetes

#26

Post by Nux »

lprd wrote: post #7

A bit off topic, but has anyone used K8s along with Proxmox?

Not a k8s user, but no reason it shouldn't work from what I read about it. Spawn a few CoreOS or RancherOS VMs and off you go.

Some people even used it with LXC, though it seems a bit of a work. e.g. https://medium.com/@kvaps/run-kubernetes-in-lxc-container-f0...

Re: K3s – Lightweight Kubernetes

#27

Post by 05 »

ithkuil wrote: post #23
zoobab wrote: post #22

Welcome to 2019 where an "embedded" system has 1GB RAM. The problem of GO is that all those unused libraries are loaded in RAM instead of staying on disk, and loaded when needed. An helloworld in GO (around 1.6MB) is still too large for my openwrt router.

Like every process, the text segment is demand paged so it doesn't consume ram unless it's actually needed. What you probably mean is that multiple copies of the same library cannot share the same physical memory pages.

Nope, they mean there's no flash memory available on the resource constrained device to store megabytes of useless runtime. Routers/other IOT Linux devices regularly use SPI ROM chips sized 4MB..16MB, you can't just install a 100MB Ubuntu/Arm rootfs on those.

Re: K3s – Lightweight Kubernetes

#30

Post by rhizome31 »

MediumD wrote: post #9
rhizome31 wrote: post #8

Earlier quoted context omitted.

What is currently a good alternative for a small business who needs to distribute containers on a handful of nodes? Docker swarm mode?

If you need to distribute containers on a handful of nodes, kubernetes is great (and far better than Docker swarm imho). However, most small businesses probably don't need to have a microservice setup and can simply deploy a simple monolith while they focus on getting their business off the ground.

Thank you. I was thinking that maybe swarm mode would be simpler to set up and maintain.

Just to give more context, our use case is spawning Jupyter notebook in containers using JupyterHub and DockerSpawner so that each data scientist gets a personal ready-to-use environment to work with. With 4 data scientists we're beginning to reach the limits of the largest instance provided by our cloud provider and we're expecting to have more users soon. Actually our current cloud provider has just released a managed k8s service so that might be the way to go.

Post reply on HN