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

41–50 of 196 posts

Re: K3s – Lightweight Kubernetes

#41

Post by packetlost »

thelastparadise wrote: post #16
mpsprd wrote: post #6

Can this tool help to simplify self hosting implems? K3s was recommended to me to replace my personal pile of systemd units starting docker compose configs and manual reverse proxy configs. Im am completely oblivious to how k8s works.

People often say kubernetes is complex, or overkill for tasks. But let's say you have many computers and want to put them to work. Suddenly, kubernetes becomes the simplest of all options. > Everything should be made as simple as possible, but not simpler . - Einstein

If that's your scenario, fine. But many put themselves in that scenario unnecessarily, which is the real problem.

Re: K3s – Lightweight Kubernetes

#42

Post by j_m_b »

Is the overhead of Kubernetes worth it enough to make it smaller, presumably to run in less resource intensive environments? Docker compose fits this bill nicely and is much more simple.

Re: K3s – Lightweight Kubernetes

#43

Post by mfer »

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.

Re: K3s – Lightweight Kubernetes

#44

Post by tarruda »

worksonmine wrote: post #32
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…

The amount of services running is not an indication of how lightweight the underlying tech is. K3S is for orchestration across nodes, and by design you can't run services on the master for security reasons unless you manually change it. Are you trying to say that 10 services and 2 nodes would be less on Nomad?

> K3S is for orchestration across nodes, and by design you can't run services on the master for security reasons unless you manually change it.

That has not been my experience with k3s. Unlike normal distributions, k3s servers do allow workload to run on them unless you manually disable. From https://docs.k3s.io/datastore/ha-embedded :

" An HA K3s cluster with embedded etcd is composed of:

    - Three or more server nodes that will serve the Kubernetes API and run other control plane services, as well as host the embedded etcd datastore.

    - Optional: Zero or more agent nodes that are designated to run your apps and services
"

So you can have a full HA k3s cluster with only 3 server nodes and 0 agent(worker) nodes.

Re: K3s – Lightweight Kubernetes

#45

Post by r-bar »

FourSigma wrote: post #21

Could someone please explain the difference between K0s[1] and K3s? They seem to both target the same minimalist K8s segment. [1] https://k0sproject.io/

K3S includes some extras that make it nice for working in small local clusters, but are not part of the standard k8s codebase.

* Traefik daemonset as a load balancer

* Helm controller that lets you apply helm manifests without the helm command line

* Upgrade controller

* Sqlite as the default backing store for the k8s API

* Their own local storage provisioner

K0S has a lot of the same goals: be light weight and self contained in a single binary. But K0S tries to be as vanilla as possible.

Choosing between the two it comes down to your use case. Do you want light weight and compatible (k0s), or lightweight and convenient (k3s)?

Edit: formatting

Re: K3s – Lightweight Kubernetes

#47

Post by efrecon »

j_m_b wrote: post #42

Is the overhead of Kubernetes worth it enough to make it smaller, presumably to run in less resource intensive environments? Docker compose fits this bill nicely and is much more simple.

Compose is for single node setups. K3s runs in multi-nodes clusters.

Re: K3s – Lightweight Kubernetes

#48

Post by ozarker »

mpsprd wrote: post #6

Can this tool help to simplify self hosting implems? K3s was recommended to me to replace my personal pile of systemd units starting docker compose configs and manual reverse proxy configs. Im am completely oblivious to how k8s works.

I use it for self hosting. It really simplified my reverse proxy config like you said. I use the internal networking between services quite a bit. I have it auto-provisioning volumes on my NAS and using them via NFS. I love it to death and would say it has simplified my setup overall. But the upfront cost of learning k8s is indeed high.

Re: K3s – Lightweight Kubernetes

#49

Post by WJW »

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 is a lightweight container orchestrator, not a lightweight Kubernetes. The whole point is to keep syntax, terminology and config options etc as similar as possible between k8s and k3s.

Re: K3s – Lightweight Kubernetes

#50

Post by yjftsjthsd-h »

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?

Post reply on HN