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

51–60 of 196 posts

Re: K3s – Lightweight Kubernetes

#51

Post by caniszczyk »

mfer wrote: post #43
imachine1980_ wrote: post #7

Why use this over kubernetes, if it's the same but less memory why not only use k3s ans drop k8s

Kubernetes is sort of like Linux. There are distributions that excel in different areas. For example, RKE2 is for those that prioritize security. It deals with compliance and security things. There are numerous distros right now. The CNCF even has a certification program and listing for the certified ones. K3s is the lightweight distro. You can install and run it from a single binary on pretty much any Linux distro.

There's 100+ certified kubernetes distros/products :)

https://www.cncf.io/certification/software-conformance/

Re: K3s – Lightweight Kubernetes

#52

Post by JohnMakin »

verdverm wrote: post #10
ge96 wrote: post #2

keees? kiots maybe

> We wanted an installation of Kubernetes that was half the size in terms of memory footprint. Kubernetes is a 10 letter word stylized as k8s. So something half as big as Kubernetes would be a 5 letter word stylized as K3s. There is neither a long-form of K3s nor official pronunciation.

So wouldn't it be K4s? I can't figure out how they got 3.

Re: K3s – Lightweight Kubernetes

#53

Post by betaby »

yjftsjthsd-h wrote: post #50
betaby wrote: post #46

Too bad k3os was abandoned. And while k3s sounds easy, it's not after even a slightly larger scale. If one willing to have in-house k8s today I would recommend https://deckhouse.io/ (I'm not affiliated with them)

> Too bad k3os was abandoned. Agreed:( Someday I'd like to see how hard it would be to use microos to build a replacement cheaply (cheap in terms of maintenance; ideally it would just be a combustion config or so that deployed k3s on vanilla microos) > And while k3s sounds easy, it's not after even a slightly larger scale. How does it fall apart?

> How does it fall apart?

Agent nodes failing to join after reboots or long network partitioning. Manual re-joining works. Additionally, hard to debug issues with the supplied Traefic.

Re: K3s – Lightweight Kubernetes

#54

Post by proxysna »

figmert wrote: post #35
diggan wrote: post #17

"Lightweight Kubernetes" and then a graph involving 2 different nodes with 10+ services running on them. Nomad seems to be a truly "lightweight Kubernetes" and for the small amount of time I've been using it, it seems to do it's job really well and it's easy to understand all the moving pieces without spending countless of hours reading docs and source code. Although, it's hard to recommend Nomad for future uses as i…

Nomad also doesn't have nearly half of the features that Kubernetes does. Need service discovery? Set up a Consul cluster. Need secret management? Install vault. Need vault enterprise? Install a separate Consul cluster! This was a few years ago, maybe it's changed? I dunno. Anyway, lightweight here means that whole bunch of external dependencies have been ripped out. E.g. AWS/GCP/Azure and I believe other things too.

You can have sd and secrets with just nomad now, it is perfect for small projects in that way.

K8s also can do secrets! base64 encoded secrets! But in case you need a more secure solution. Please pull in a Vault helm chart or mess around with sops or whatever. Want to scale out? See how long it will take you until you will have to move your etcd to dedicated hw/vm's. And let me tell you - setting up external etcd in prod sucks. Also maintaining mission control, because there is a bunch of ways to do things and devs love using things that they are not supposed to touch.

Nomad approach is modular this is why it works. Need proper multi dc SD? please run a consul cluster (single binary + single config file)x3. Need mesh networking? same. Need secrets? Vault (single binary + single config file)x3. Pki? same. Or maybe you don't need it? Then you have an option to just not use it.

One thing that i really don't like about it that there is not a lot of docs describing all the ways these tools can interact with each other.

Re: K3s – Lightweight Kubernetes

#55

Post by maxbond »

JohnMakin wrote: post #52
verdverm wrote: post #10

Earlier quoted context omitted.

> We wanted an installation of Kubernetes that was half the size in terms of memory footprint. Kubernetes is a 10 letter word stylized as k8s. So something half as big as Kubernetes would be a 5 letter word stylized as K3s. There is neither a long-form of K3s nor official pronunciation.

So wouldn't it be K4s? I can't figure out how they got 3.

They're counting the "k" and the "s" to get to 5 total. It's a bit more convoluted than 4 = 8 / 2, it's 3 = (8 + 2) / 2 - 2.

Re: K3s – Lightweight Kubernetes

#56

Post by proxysna »

_w1tm wrote: post #40
diggan wrote: post #17

"Lightweight Kubernetes" and then a graph involving 2 different nodes with 10+ services running on them. Nomad seems to be a truly "lightweight Kubernetes" and for the small amount of time I've been using it, it seems to do it's job really well and it's easy to understand all the moving pieces without spending countless of hours reading docs and source code. Although, it's hard to recommend Nomad for future uses as i…

> Nomad seems to be a truly "lightweight Kubernetes" and for the small amount of time I've been using it, it seems to do it's job really well and it's easy to understand all the moving pieces without spending countless of hours reading docs and source code. Does Nomad expose an API that you can extend with controllers running inside the cluster? Because Kubernetes without operators is not Kubernetes.

yes, you can do that. Here's an example. https://andydote.co.uk/2021/11/22/nomad-operator-pattern/

Re: K3s – Lightweight Kubernetes

#58

Post by willaaam »

mfer wrote: post #34
BossingAround wrote: post #20

Interestingly, SUSE now owns Rancher [0], so k3s has been backed by a large company for some time now. I've never tried k3s, but I have always thought it's probably the most loved-by-its-users version of Kubernetes. [0] https://www.suse.com/news/suse-completes-rancher-acquisition...

If you want to easily try it out, we baked it into Rancher Desktop [1]. RD let's you run Kubernetes (via k3s) and containers on your desktop. You pick the k8s version. [1] https://rancherdesktop.io/ Disclosure, I work for SUSE and started Rancher Desktop.

I just made an account here to say thank you. Rancher desktop is amazing on my M2 mac, it's easy to use, solves a bunch of challenges from k8s to docker and has been surprisingly reliable for a young product.

Re: K3s – Lightweight Kubernetes

#59

Post by worksonmine »

JohnMakin wrote: post #52
verdverm wrote: post #10

Earlier quoted context omitted.

> We wanted an installation of Kubernetes that was half the size in terms of memory footprint. Kubernetes is a 10 letter word stylized as k8s. So something half as big as Kubernetes would be a 5 letter word stylized as K3s. There is neither a long-form of K3s nor official pronunciation.

So wouldn't it be K4s? I can't figure out how they got 3.

Cut the 8 in half and you get 3, not mathematically but visually.

Re: K3s – Lightweight Kubernetes

#60

Post by withinboredom »

mfer wrote: post #34
BossingAround wrote: post #20

Interestingly, SUSE now owns Rancher [0], so k3s has been backed by a large company for some time now. I've never tried k3s, but I have always thought it's probably the most loved-by-its-users version of Kubernetes. [0] https://www.suse.com/news/suse-completes-rancher-acquisition...

If you want to easily try it out, we baked it into Rancher Desktop [1]. RD let's you run Kubernetes (via k3s) and containers on your desktop. You pick the k8s version. [1] https://rancherdesktop.io/ Disclosure, I work for SUSE and started Rancher Desktop.

I've honestly been scared to switch from Docker Desktop to Rancher Desktop on Windows. Like do I have to switch or do they play nice together? Do I need to install Docker in WSL to use it, or kubectl, or is it like Docker Desktop where it "just works."

So many questions...

Post reply on HN