Thanks, but I think you missed the most important features of either distri. On k0s you have a nice yaml definition with a lot of options like running kube-router instead of flannel etc. But not only that, you have the option to run the master as a hidden node that won't be seen by the cluster and the nodes connect to it via a proxy. This enables running it in very constrained environments and in LXC containers as it doesn't host any kind of containers. K3s on the other hand has a very optionated install with welcoming features like clipper lb or a slim host path provisioner. The features also have to be disabled explicitly on each node. That's what's imho the interesting/important part. The installation itself should not be taken in account as they're both very easy and pretty similar.
I missed something or you just didn't answer your question? Which one is better for home use? What are the differences between them? Or just the name is biggest difference?
@@Sivarion kuberentes is a massive overkill for smaller projects. You will end up having to maintain massive yaml files, which will not provide any value to you. Furthermore kubernetes is a massive resource hog, the resources needed for your applications will be multiplied just to be on par with what you currently have.
@@junit1606 oh, yes, in that case - you are 100% right. There is no point in using kubernetes for personal project other than to learn kubernetes along the way - this is why I do it.
@fin31337, either should work, sometimes I have so many VMs in the lab with different logins configured. I should have standardized to show both using sudo.
@squalazzo, thank you for your comment! I really like k3d and have used it / written about it before: www.virtualizationhowto.com/2022/04/install-k3s-on-ubuntu-with-k3d-in-docker/. For this though, I wanted to compare vanilla k0s and k3s running them in the same way. Hope this helps!
@@squalazzo yeah but I use ansible for everything. Even if it's not needed. I just love seeing it work away as I drink my coffee ☕. But the best part is how it can be cleaned up so easily.
![🔴 ฟุตบอลแชมป์กีฬา 7HD แชมเปียน คัพ 2024 [รอบรองชนะเลิศ]](http://i.ytimg.com/vi/zPm8ClLVhoE/mqdefault.jpg)
Thanks, but I think you missed the most important features of either distri. On k0s you have a nice yaml definition with a lot of options like running kube-router instead of flannel etc. But not only that, you have the option to run the master as a hidden node that won't be seen by the cluster and the nodes connect to it via a proxy. This enables running it in very constrained environments and in LXC containers as it doesn't host any kind of containers. K3s on the other hand has a very optionated install with welcoming features like clipper lb or a slim host path provisioner. The features also have to be disabled explicitly on each node. That's what's imho the interesting/important part. The installation itself should not be taken in account as they're both very easy and pretty similar.
exactly
What you're taking abt , I can understand and cant understand at the same time
So which is the best?
I missed something or you just didn't answer your question? Which one is better for home use? What are the differences between them? Or just the name is biggest difference?
Avoid both for home use
@@junit1606 thanks! Do you mind expaining why and what do you suggest as alternative?
@@Sivarion kuberentes is a massive overkill for smaller projects. You will end up having to maintain massive yaml files, which will not provide any value to you. Furthermore kubernetes is a massive resource hog, the resources needed for your applications will be multiplied just to be on par with what you currently have.
@@junit1606 oh, yes, in that case - you are 100% right. There is no point in using kubernetes for personal project other than to learn kubernetes along the way - this is why I do it.
@@junit1606 Yes, but don't you think k3s has a relatively low overhead? It's even used in IoT projects due to its lightweight nature.
Excellent: Best HS deployment tutorial I ever watched!
Which uses less CPU and disk IO? k3s uses about 1CPU for the control plane... curious to see how k0s fairs...
Thanks for the demo and info, have a great day
So where is answer?
Very interesting - could you mix and match? Any advantage in having k8s controller and k3s workers for example please?
Could you please provide some insights why did you use sudo to install K0s and root to install k3s?
Should it been run only with privileges?
@fin31337, either should work, sometimes I have so many VMs in the lab with different logins configured. I should have standardized to show both using sudo.
@fin31337, if you have further questions, be sure to sign up on the VHT forums here: www.virtualizationhowto.com/community
Thanks B.L.
why not k3d (which uses k3s underneath)? very easy to use, with integrated traefik to expoxe services, if needed, and localpath as csi driver
@squalazzo, thank you for your comment! I really like k3d and have used it / written about it before: www.virtualizationhowto.com/2022/04/install-k3s-on-ubuntu-with-k3d-in-docker/. For this though, I wanted to compare vanilla k0s and k3s running them in the same way. Hope this helps!
@@VirtualizationHowto thanks, i'll take a look :)
I use ansible k3s. One click and setup a ha cluster on as many nodes as you want. It's very nice 👍
@@hotrodhunk7389 same does k3d and no ansible needed
@@squalazzo yeah but I use ansible for everything. Even if it's not needed. I just love seeing it work away as I drink my coffee ☕. But the best part is how it can be cleaned up so easily.
Have you already consider OKD as a next candidate for your lab ? This is open source version of OpenShift
Okd is pretty cool and has some amazing features, but it needs a ton of Ram 😂
what is k0s?
Into music is way too loud
The word "into" doesn't have enough "r"''s 😊
@@MartinPHellwig well …
I hate background music while someone is speaking. Don't get it at all. Even worse it's too loud.