9 ms·
K3s: Kubernetes without the features I don't care about
- infogulch 8y agoNot sure what it is, but the name really tickles me. Bonus points that it's kinda meta.
- geoah 8y agoIt's a cut-down version of kubernetes. Author left the basic features and removed most things that are oriented to heavier users or that required more resources than they wanted to spare. I assume the goal is to make k3s into something light where you can deploy small projects instead of using something like swarm/dokku. He has also removed etcd and replaced it with sqlite which seems like a nice way to reduce resource requirements.
- vemv 8y agoPresumably some of those features will be relevant to you as you scale. Also, ignoring a feature seems far cheaper than forking a project and renouncing to updates for desired features? e.g: feat A is desired, feat B is not, a new upstream refactor touches A and B. How do you stay up-to-date?
- eganist 8y agoWhat do you have against Rnete?
- darren0 8y agoAgainst Kubernetes? Nothing, it's a beautiful architecture. I just want to use the code and architecture in different ways and specifically with lower resource constraints.
- eganist 8y agoOh, I was merely making light of the name "kubes" which I figure is what you meant with the numeronym. Apologies that my dog couldn't hunt.
- chrisseaton 8y ago> Apologies that my dog couldn't hunt. Huh?
- troygoode 8y agoIts an American English idiom, in this case referencing his joke not performing the intended job of making you laugh. https://english.stackexchange.com/questions/52755/meaning-and-origin-of-that-dog-dont-hunt https://english.stackexchange.com/questions/52755/meaning-an...
- wink 8y agothis is getting real meta now :) Thanks for the explanation.
- deleted 8y ago[deleted]
- darren0 8y agoI created this (I'm the Chief Architect and Co-founder of Rancher Labs, I experiment with stuff like this all the time). The purpose of this project is really to embed in another project (https://github.com/rancher/rio https://github.com/rancher/rio is an example) but as a side effect it's a nice little standalone k8s package. I never had any intention to support it as a standalone project, but hey if somebody is interested who knows. All of the features removed are based off of two basic ideas 1) If there are X ways to do something, I choose the best one (obviously subjective). 2) The features are not commonly used or really shouldn't be in k8s to begin with. The end goal of what I'm working on is basically to use k8s code as a library to do orchestration. Step one was to reduce the footprint of k8s (I'm 80% there with this project), step two is to completely rework the state management such that you no longer need to persist state in k8s. This is a much larger goal. I've fooled around a lot with the persistence layer in k8s (this project is running on sqlite3) so I'm basically doing a lot of work of figuring what state I can throw away. The theory is that all desired state comes from your yaml files. Actual state is actual (what really exists). Everything else in k8s should be purely derived and not important.
- nwmcsween 8y agoOT but why do you want to push containers? In my opinion it's a misadventure from the real issue of a proper package manager (which in turn is a misadventure from a proper build system) The issue with current containers is it's the wrong level of abstraction, containment should be per binary and ideally inline with code (see pledge(2)).
- barrkel 8y agoK8s is about cluster orchestration. It's for building apps that allocate memory and compute from a pool of machines almost like malloc() and free(). It's also an abstraction for allocating compute away from the specifics of a provider, so you theoretically don't care if you deploy to gcloud or Azure or AWS. Containers and images merely define the interface with the agnostically allocated compute. They're not the essential bit though, not the magic.
- xrd 8y agoThis is such a great stepping stone to playing with k8s. Maybe there should be a book with each chapter named k1s, k2s, k3s. Each chapter introduces more and more features with the why of each. Eventually you get to the full set of features and can use k8s in its entirety.
- qohen 8y agoSpeaking of "a great stepping stone to playing with k8s", there's a free, scenario-based site called KataCoda.com out there that gets you putting Kubernetes (and Docker and other things like TensorFlow) through its paces -- no need to install anything, it's all browser-based. The site also has some "playgrounds" for experimentation once you know what you're doing and apparently can be used to create one's own courses, e.g. for training people at your company, etc. List of all the courses: https://www.katacoda.com/learn https://www.katacoda.com/learn
- crb 8y agoI more than get the joke, but I'm worried about the ambiguity of "5 less then k8s. Short for kates, pronounced k8s", and worry that it will stop you from getting successful, if that's your intention. Are you saying your project is named "kates"? Why not name it something like "Khios", a Greek island, which still lets you keep 'k3s' as your abbreviation?
- darren0 8y agoI never intented anyone to directly use it. The "selling point" is what I'm going to put on top of this. This is intended to be an internal library. Hence the stupid puny name.
- dsnuh 8y agoHow about "k2s", short for "K.I.S.S."? So simple it saves you an S. :)
- linuxdude314 8y agoKubernetes == K8s, not his project.
- pcmaffey 8y agoI can't wait for someone to come out with a product called `k8OS`
- stevenacreman 8y agoCurious if this would be better than minikube when running in a CI pipeline to run tests on.
- bboreham 8y agoI salute the enormous amount of work you’ve done. But without a consistent store, it seems to me there are a myriad of race conditions the system can fall into. Maybe if you accept a bit of oscillation under stress, and damp that oscillation a lot, it would be ok.
- mosselman 8y agoFor years now my favourite way to deploy my own 'side-projects' has been Dokku. It is like having your own Heroku on a single machine. Very neat, but no clustering. Lately I have been playing with kubernetes and now docker swarm. I must say that I too find kubernetes to be too heavy (feature- and concept-wise) for the smaller scale things that I am up to: I have to read up too much, learn too many new concepts, write too many config files. Docker swarm is a lot more appropriate for scaling those side-projects to a slightly bigger step, however, I have concerns about the longevity of the project. Will Docker Swarm still exist in 5 years?
- ngrilly 8y agoThe biggest issue I have with Kubernetes is it doesn't downscale. I have a lot of projects that don't need a cluster. A single node is enough. But Kubernetes has too much CPU and RAM overhead in such a configuration. Because of this, I'm forced to either use another orchestrator (Docker Swarm is lightweight enough to work on a single node or a small cluster), or pay for machines I don't really need. What are is the current thinking on this issue at Rancher?
- hauxir 8y agohave you tried dokku? https://github.com/dokku/dokku https://github.com/dokku/dokku
- ngrilly 8y agoApps are usually composed of several services working together, each service being in its own container. I'd like to be able to use something like docker-compose.yml to describe this. And it looks like Dokku doesn't do this.
- falcolas 8y agoHave you considered stepping back and wondering if you really need orchestration at this scale? Couldn't a simple unit file suffice? If you have many such projects, perhaps something like Saltstack or Ansible, both of which have support for Docker container management built in.
- ngrilly 8y agoGreat question! I already use Ansible to setup machines and automate deployments. I used systemd unit files until I switched to Docker. I don't use them anymore since dockerd supervises the container itself. I use Docker Compose to describe the set of services composing my app and it's great. But in production, Docker Compose is unable to provide zero-downtime deployments, and this is why I'm looking at Docker Swarm or Kubernetes. systemd unit files are not very useful for Docker containers, and they don't solve the zero-downtime deployment issue.
- 8y ago