Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

K0s – Zero Friction Kubernetes

github.com

Post reply on HN
Print view View original

61–70 of 78 posts

Re: K0s – Zero Friction Kubernetes

#61

Post by neurostimulant »

stavros wrote: post #10
watermelon0 wrote: post #7

Earlier quoted context omitted.

K3s 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.

Ah, I see, thank you. Sounds like just manually starting docker-compose stuff will be preferable right now.

Docker compose is certainly enough for personal use, but if you ever want your apps to be available during update process (on docker compose you'll have to shut down your app container before you can update it), it's very easy to setup a basic blue/green deployment using the readiness probe option in kubernetes.

Also, kubernetes load balancer is pretty easy to setup and plays well with multiple services and letsencrypt. On docker compose, I'll have to either use nginx and update it everytime I add more apps or use something like traefik if I want a load balancer that can read configuration from app's label. On kubernetes you simply specify several lines of ingress definition in your yaml file, which is not too complex for a typical app.

Re: K0s – Zero Friction Kubernetes

#62

Post by devonkim »

ralph87 wrote: post #34
oneplane wrote: post #12

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 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 a…

A 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.

Re: K0s – Zero Friction Kubernetes

#63

Post by ncopa »

dastx wrote: post #25

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!

To be fair, the most significant parts are done by the other team members.

Re: K0s – Zero Friction Kubernetes

#64

Post by oarsinsync »

pcjthug wrote: post #50
stonewareslord wrote: post #31

Earlier quoted context omitted.

Technically, it would be an undefined number of times easier. n/0 is not infinite.

Technically, 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

I 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.

Re: K0s – Zero Friction Kubernetes

#65

Post by dastx »

ncopa wrote: post #63
dastx wrote: post #25

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!

To be fair, the most significant parts are done by the other team members.

Sorry, didn't mean to diminish the other team members' contributions. It's just your name stood out to me.

Re: K0s – Zero Friction Kubernetes

#66

Post by sam0x17 »

soneil wrote: post #16
sam0x17 wrote: post #15

So question I've always had -- where does the 8 in k8s come from? It has never been self-evident for me :/

It’s a contraction of the inner 8 letters. In the same vein as i18n.

And now I understand why i18n is named the way it is!!!!! This has been very illuminating

Re: K0s – Zero Friction Kubernetes

#67

Post by cassianoleal »

dheera wrote: post #30
tonyjstark wrote: post #2

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)!

k8s 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.

It'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

Re: K0s – Zero Friction Kubernetes

#68

Post by MrBuddyCasino »

ccmcarey wrote: post #42
MrBuddyCasino wrote: post #39

Earlier quoted context omitted.

> 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.

Correct, but there's no need to use autism as an insult or imply (only) they do that.

Exactly nobody asked for your virtue signalling.

Re: K0s – Zero Friction Kubernetes

#69

Post by zerkten »

StavrosK wrote: post #47
zerkten wrote: post #37

Earlier quoted context omitted.

I just came across caprover ( https://caprover.com/ .) I've heard mixed things about Dokku and was going to try it out.

I really like Dokku, if you're running straight-up websites it's fantastic and very reliable. Any other configuration, it's not really designed for.

Are you hosting any databases in Dokku, or do you keep data outside? For a very small PaaS keeping the DB on a separate node feels like the most reliable option.

Re: K0s – Zero Friction Kubernetes

#70

Post by StavrosK »

zerkten wrote: post #69
StavrosK wrote: post #47

Earlier quoted context omitted.

I really like Dokku, if you're running straight-up websites it's fantastic and very reliable. Any other configuration, it's not really designed for.

Are you hosting any databases in Dokku, or do you keep data outside? For a very small PaaS keeping the DB on a separate node feels like the most reliable option.

I used to host them in Dokku but switched to outside because it's just so much more convenient to have everything in one database. I keep it on the same node, but yes, definitely outside. I have one redis outside too, rather than one per project.
Post reply on HN