Could someone please explain the difference between K0s[1] and K3s? They seem to both target the same minimalist K8s segment.
K3s – Lightweight Kubernetes
21–30 of 196 posts
Re: K3s – Lightweight Kubernetes
#22Why use this over kubernetes, if it's the same but less memory why not only use k3s ans drop k8s
There's no real "over kubernetes". K3s is a kubernetes implementation. You have to think of k8s as more of a specification of what can be done with multiple implementations. k3s, kind, microk8s, minikube are all implementations of kubernetes that you might want to try out. k8s is much like the original IBM pc or a linux distribution. There are a bunch of interchangeable parts that you may land on depending on your ne…
So all of those can be used to host a highly available multi physical node cluster?
Re: K3s – Lightweight Kubernetes
#23forget about it if you want to run it on an IPv6-only VPS, it's not ready yet
There's not any common reason I can think of to go ipv6 on the backend. KISS --if there's enough IPs in a private v4 range, use them.
If you need/want to serve v6 clients, put a v6 load balancer in front. You're likely going to need that lb anyway.
Re: K3s – Lightweight Kubernetes
#24Anyone running K3S on Hetzner's new ARM64 servers?
Re: K3s – Lightweight Kubernetes
#25keees? 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.
I always prefer to spell it kUbernEats.
Re: K3s – Lightweight Kubernetes
#26forget about it if you want to run it on an IPv6-only VPS, it's not ready yet
There's not any common reason I can think of to go ipv6 on the backend. KISS --if there's enough IPs in a private v4 range, use them. If you need/want to serve v6 clients, put a v6 load balancer in front. You're likely going to need that lb anyway.
I think the use case was running on a cheap server that actually doesn't have ipv4 connectivity
Re: K3s – Lightweight Kubernetes
#27Can 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.
K3s/k8s may help with that, but it's going to be a learning curve. I personally moved onto k8s for a similar reason, but it was a learning curve
It's a learning curve, but it is consistent, reliable, and standardized.
Kubernetes has become an interface, independent of implementation.
It's much like how POSIX is a standard and there are many implementations.
And yes, POSIX has a learning curve too, but I'd rather learn that than anything proprietary, or non standard/rapidly changing.
Re: K3s – Lightweight Kubernetes
#28Why use this over kubernetes, if it's the same but less memory why not only use k3s ans drop k8s
There's no real "over kubernetes". K3s is a kubernetes implementation. You have to think of k8s as more of a specification of what can be done with multiple implementations. k3s, kind, microk8s, minikube are all implementations of kubernetes that you might want to try out. k8s is much like the original IBM pc or a linux distribution. There are a bunch of interchangeable parts that you may land on depending on your ne…
Yes. I think Kubernetes "distribution" has always made the most sense to me.
Re: K3s – Lightweight Kubernetes
#29"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…
I mean, 2 nodes and 10 services is very light for what Kubernetes is designed to scale to.
Re: K3s – Lightweight Kubernetes
#30K3s is fantastic especially for local development with Kubernetes when orchestrated using k3d. This is what we use for most of our internal K8s testing at OpenC3.
Yes, I recently moved my Dev team to K3D as well. Previously we were using AWS clusters that were spun up on demand every time someone needed to test something. the time needed to do this grew and grew overtime eventually coming close to 30 to 40 minutes. With k3d testing locally can be done in a minute. Plus I learned a ton about k8s while doing this.