Live data from Hacker News

K0s – Zero Friction Kubernetes

github.com

51–60 of 78 posts

Re: K0s – Zero Friction Kubernetes

#51
post #30

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.

I read it as "Kate's" and say that out loud occasionally and am understood

Re: K0s – Zero Friction Kubernetes

#52
post #18

Earlier quoted context omitted.

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

I went to go and re-instate your edit. When I got there, exactly where it was, someone's now put in a citation to an article that explains the answer perfectly: https://medium.com/@rothgar/why-kubernetes-is-abbreviated-k8... Wikipedia is great, and people like you make it that way, thank you :)

Yes, I think link [1] is better at showing its history. Personally I was exposed to e10s from Firefox before leaning about the who a11y and all other xNumberx Terms.

[1] http://www.i18nguy.com/origini18n.html

Re: K0s – Zero Friction Kubernetes

#53
>"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.

Re: K0s – Zero Friction Kubernetes

#54
post #16

Earlier quoted context omitted.

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

Or a11y for accessibility.

I 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

Re: K0s – Zero Friction Kubernetes

#55

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

[deleted]

Re: K0s – Zero Friction Kubernetes

#56

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

Pronouncing 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 grap…

As a native Hebrew speaker, when I was first exposed to Kubernetes years ago I could not have overlooked the resemblance to the Hebrew word "kbarnit" which has the same meaning. I'm sure the Greek word which inspired the authors and the Hebrew word share origins (don't know which predates the other), but in this case the Hebrew word happens to sound closer to the common pronunciation which helped me pick it up quite intuitively

Re: K0s – Zero Friction Kubernetes

#57
post #50

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

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

Re: K0s – Zero Friction Kubernetes

#58
post #6

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?

You might check out Okteto [1] -- it's a very nice service, nice free tier for checking it out.

[1] https://okteto.com

Re: K0s – Zero Friction Kubernetes

#59
post #18

Earlier quoted context omitted.

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

I went to go and re-instate your edit. When I got there, exactly where it was, someone's now put in a citation to an article that explains the answer perfectly: https://medium.com/@rothgar/why-kubernetes-is-abbreviated-k8... Wikipedia is great, and people like you make it that way, thank you :)

That was there when I added it, I think I thought it was just a citation for it being referred to as 'k8s'. I left the citation there but added to '(commonly stylized as k8s', ', a [[numeronym]]'.

It was removed for being 'distracting trivia': https://en.wikipedia.org/wiki/Special:MobileDiff/945525973

:shrug: I thought it was pretty innocuous, succinctly explaining it and linking to a page with more examples for those curious.

I suppose the pace would be too much slower, but I really wish Wikipedia had more of a 'maintainer'-'change request' model (a la GitHub etc. or even mailing lists) sometimes, so edits had to actually be justified and approved.

StackExchange has a reasonable compromise I suppose - you're automatically a 'maintainer' with certain (quite low) karma, and until then your changes are proposed and can be (but generally not) justified per se, and approved by someone who does have sufficient points; then you get some points if its approved.

Re: K0s – Zero Friction Kubernetes

#60
post #20

Earlier quoted context omitted.

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

This is for Docker, right? Not Compose? Though I guess Compose would just set the flag in Docker, in which case it'd do the same thing. I don't want more granularity than "unless stopped", basically, so this is ideal, thanks!

Docker-compose is just a wrapper by itself. It just make volumes, port forwarding, etc based what you you will describe in your docker-compose file.

So if you have proper Docker installation, containers will restart on reboot.

Post reply on HN