10 ms·
K0s – Zero Friction Kubernetes
- bithavoc 6y agoThe name seems to imply this project is 3x smaller than K3S[0], does it use less memory, CPU? If this is all about removing external dependencies, I don't think is worth creating an entire new project to avoid installing something like `socat`. [0]https://k3s.io/ https://k3s.io/
- phist_mcgee 6y agoTechnically it is infinite times smaller than k3s or k8s :)
- stonewareslord 6y agoTechnically, it would be an undefined number of times easier. n/0 is not infinite.
- pcjthug 6y agoTechnically, we may consider k0s to be the limit of a decreasing sequence of container orchestrators `k8s, k3s, ... = k{x}s as x -> 0` in which case we have 8/x -> +inf
- kimburgess 6y agoTechnically, neither the limit or full progression is defined by the information available. The set {k8, k3, k0} may be equally represented as a decreasing series of container orchestrators with reducing prime differences.
- oarsinsync 6y agoI always thought that k3ks was so named because the symbol for 3 looks like a partial symbol for 8, indicating that it's k8s with a bit less.
- pas 6y agok3s recently switched to embedded etcd, so if you want something very lightweight out of the box (yet with HA), try Canonical's microk8s it has dqlite support.
- darren0 6y agok3s still defaults to sqlite. For HA dqlite was dropped in favor of embedded etcd in k3s 1.19.
- tonyjstark 6y agoIs it just me or do other people also read the name as `chaos`? I guess with k8s one hard part is to get it well-configured up and running and the other to maintain it and adjust to the project's needs. But seems the project tries to improve the whole experience. Good luck (honestly)!
- dheera 6y agok8s always tripped me up, personally. I always mentally read it as "k-ubereats" (kind of like "k-means"), so it always effectively started with a "u" to me.
- comradesmith 6y agoI read it as "Kate's" and say that out loud occasionally and am understood
- cassianoleal 6y agoIt's supposedly k-eight-s. It means the letter "k", eight other letters, and the letter "s". Similar to i18n for internationalization and l10n for localization. Surely you don't pronounce those as ieighteenn and eltenn, right? :D
- abqexpert 6y agoI read it as k-aughts and k8s as k-eights, and all my juniors have at first as well. These aren't great abbreviations, we just get used to them. My main issue with this project is that if you want to use k8s and are using it, you want some measure of control. Unless you are just using it "because", your business goals intersect with the k8s philosophy and you need some element of it. In every case I have deployed it in there is a lot of fine tuning.
- pantelisk 6y agoPronouncing kubernetes was a problem for me as a greek (greek way would be kee-vaer-nee-tees and it means governor). Getting my mind to use the english word tripped me out, and using the greek pronunciation didn't make sense to anybody. Since trying to say "kubernetes" just trips my mind, I say kubernet (coobearnet). And use the same term "kubernet" for both "kubernetes" and the "k8s" shortcut. Kubernet = "k for graph (eg k-anonymity, k-neighbor search), uber for awesome, net for network!" It's a very descriptive and easy to pronounce/memorize name that frees my mind from the greek pompousness. PS. k0s, I would pronounce "Cause" or maybe... (to make a silly bloodborne reference) Kos, some say Kosm
- dryicerx 6y agoWhat differentiates this from k3s? Seems like there's a lot of overlap. Would be great if there was a quick summary of why someone would use this instead of k3s/microk8s/minikube/etc.
- dryicerx 6y agoSome googling satisfied my curiosity about the k0s vs. k3s https://www.reddit.com/r/kubernetes/comments/jumaqj/k0s_yet_another_kubernetes_distribution_by/ https://www.reddit.com/r/kubernetes/comments/jumaqj/k0s_yet_... https://medium.com/@saiyampathak/k0s-yet-another-kubernetes-distro-7201ea425165 https://medium.com/@saiyampathak/k0s-yet-another-kubernetes-...
- yjftsjthsd-h 6y agoBased on the medium post: Is FIPS compliance a good thing? I was under the impression that FIPS sometimes... lagged... modern ideas about security, such that if you weren't for some reason mandated to use it then it was either neutral or bad.
- StavrosK 6y agoHas anyone used K3s or this? Are they a good alternative to Dokku? I'm looking for something to either deploy on a server to host all my sideprojects (though Dokku has been basically perfect so far), or on my home server for various things like Gitea, Nextcloud and random scripts. Is K3s/K0s a good idea for either of those?
- watermelon0 6y agoK3s is definitely more lightweight than K8s, but it still requires non-negligible resources. Compared to just a Docker engine, it takes more memory and CPU, which can be noticeable on smaller servers, Raspberry Pi, and such.
- StavrosK 6y agoAh, I see, thank you. Sounds like just manually starting docker-compose stuff will be preferable right now.
- tinco 6y agoI'd make systemd unit files around the docker-compose deployments. Upload everything with something like Ansible. If you want to go perfect go for NixOS instead, but that might be controversial.
- StavrosK 6y agoDoesn't Compose take care of that with "restart: always"? Though that probably doesn't work on reboot...
- 0_gravitas 6y agoIt does!
- easton 6y ago"restart: always" and "restart: unless-stopped" both work fine after reboot on my system. (Although Docker recommends managing it using systemd or upstart if you want more granular control). https://docs.docker.com/config/containers/start-containers-automatically/ https://docs.docker.com/config/containers/start-containers-a...
- oneplane 6y agoI don't understand why people seem to want K8s but then find it 'difficult'. It's really not that complex, and when you add stuff on to it, that is your own choice (just like with k3s and k0s). You essentially end up with a kubelet, apiserver (with etcd) and two or three copy-and-paste YAML files (manifests) to setup a 'full' k8s cluster. If that is too much, is k8s even relevant to your case? Say your workload is so small and so simple that having a minimum of 2 servers isn't what you want, then again, is k8s even relevant for your case? Or perhaps the better question: who is this for?
- ralph87 6y agoKubernetes does a whole lot more than just restart jobs when a node fails, in fact of all its features this is one most people probably see in action the least. Kubernetes centralizes all the traditional technical nonsense related to providing a robust environment to deploy applications to. I want Kubernetes even in a single node scenario because I want Kubernetes-like packaging, deployment and network services for any app I work on, as they are a net simplification of what was previously an ad-hoc world of init scripts, language-specific supervisors, logging, monitoring, etc etc., and rearchitecting an app deployment from scratch simply because its resource requirements increased. If people want to continue trying to scale it down further, where is the harm in this? There are plenty of legitimate cases where it makes sense. There's no real limit to that work either, it's conceivable with the right implementation improvements (in k8s and the container runtime), it might eventually be possible to reuse the same deployment model even for extremely small devices.
- devonkim 6y agoA lot of people seem to miss that one of the primary points of using K8S is that it’s a PaaS. Instead of relying upon cloud provider based services one could use K8S constructs and make it easier to port applications and services across hosting providers. The lock-in factor is a point of nervousness not because people consider wanting to move from AWS but because it can be hard to port new features supporting providers concurrently if every developer immediately reaches for the provider’s message queue, e-mail service, batch processing pipeline, etc. It takes a lot of effort to learn these various services’ nuances and that’s not necessarily useful for everyone. And while K8S maintenance is fairly involved, trying to do deployments and system administration in its absence (read: production grade applications packaged prior to containers) is expensive and extremely error-prone as well. As much as it’s a pain to deal with a mangled K8S setup, it absolutely beats 20+ idiosyncratic applications wired their own particular way with oddball service hacks on a snowflake server. This is a huge business liability that is changed at least to random containers in a container-based ecosystem of applications.
- sam0x17 6y agoSo question I've always had -- where does the 8 in k8s come from? It has never been self-evident for me :/
- soneil 6y agoIt’s a contraction of the inner 8 letters. In the same vein as i18n.
- b0afc375b5 6y agoOr a11y for accessibility.
- gitgud 6y agoI feel like an idiot for not knowing this!! I assumed it was a meaningless name that some standard's body assigned, like ISO9000 or AS200
- sam0x17 6y agoAnd now I understand why i18n is named the way it is!!!!! This has been very illuminating
- OJFord 6y agoThis is such a common question that I was motivated to add it to the Wikipedia page. Unfortunately, someone decided to revert it. 'k8s' is a numeronym: the '8' denotes eight omitted letters ('ubernete'). https://en.m.wikipedia.org/wiki/Special:MobileDiff/943694377 https://en.m.wikipedia.org/wiki/Special:MobileDiff/943694377
- MrBuddyCasino 6y ago> someone decided to revert it The Wikipedia consensus protocol works like this: The autist with the most free time and the biggest urge to control wins. You'll have to out-edit the guy who made that specific page his fiefdom and Raison d'être. Good that you tried, I've decided its not for me.
- dastx 6y agoSeems the person with the most contributes is Natanael Copa, who is also one of the lead maintainers of Alpine Linux Distribution. Pretty cool! I look forward to the first stable release!
- hardwaresofton 6y agoI didn't notice this, and this is a huge factor for raising my own interest. Natanael is prolific. The project already piqued my interest because I think of kubernetes' main problems can be how hard it is to hold all the actual binaries that need to run in your head, but I think the real test will be how it migrates/upgrades. The "don't break user space" stability of projects like linux and postgres would be a game-changer in the cloud native space.
- ncopa 6y agoTo be fair, the most significant parts are done by the other team members.
- dastx 6y agoSorry, didn't mean to diminish the other team members' contributions. It's just your name stood out to me.
- deleted 6y ago[deleted]
- captn3m0 6y agoI noticed that the project has a Copyright Mirantis at the bottom. Pretty nice to see them getting here, after the Docker acquisition.
- bogomipz 6y ago>"Some of the high level goals of the project: Elastic control-plane" I would be interested in hearing more how this works. Is there something like the Cluster Autoscaler and an HPA that scales up control plane pod and nodes? I'm curious if the author(s) considered leveraging Hyperkube for this project and why or why not if so. This looks interesting so far though.