31–40 of 78 posts
The 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/
Technically it is infinite times smaller than k3s or k8s :)
Is 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)!
I 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…
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.
Seems 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!
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.
Has 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?
I like the fact that I can run the same stack on my laptop and the cloud
Has 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?
The 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/
k3s 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.
So question I've always had -- where does the 8 in k8s come from? It has never been self-evident for me :/
This 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
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.
Earlier quoted context omitted.
I’m a fan of Hashicorp Nomad (coupled with Vault and Consul). It’s a matter of preference though, if you love the kubernetes abstractions and APIs you’re probably better off with k3s/k0s. I personally very much prefer Nomads less obfuscating abstraction layers. This is coming from 2-3 years of managed k8s at work. It does take a bit of effort to set up ”properly“ - ideally each of vault/consul/nomad server should run…
This was one of the most surprising parts about Nomad for me. I really want to like it, and for the most part I think it's a great experience, but if you're looking for a lightweight single-host PaaS-type thing, the minimum recommendation and default configuration for 3 servers is a bit wild. I have Nomad running in single host mode on a DO box for personal stuff, and I get the distinct feeling I'm not really meant t…