71–80 of 90 posts
Earlier quoted context omitted.
Kubernetes is often shortened to k8s, which is often pronounced "kates," which is further shortened to k3s.
Isn't it actually keigths which means it should be k5s?
k3s is a pared down version of k8s, which is illustrated by the number 3 being chosen because it looks like an 8 sliced in half.
Earlier quoted context omitted.
Isn't it actually keigths which means it should be k5s?
Kubernetes reads like kubern-eight-es so k8s is the shorthand. k3s is a pared down version of k8s, which is illustrated by the number 3 being chosen because it looks like an 8 sliced in half.
"What's with the name?
We wanted an installation of Kubernetes that was half the size in terms of memory footprint. Kubernetes is a 10-letter word stylized as K8s. So something half as big as Kubernetes would be a 5-letter word stylized as K3s. There is no long form of K3s and no official pronunciation."
Title is misleading. k3s is a deployment stack/distribution that builds off various Kubernetes modules. It must pass a certain test suite to conform to Kubernetes standards. What you might be trying to compare is kubeadm which is the official deployment stack provided by Kubernetes.
Ok, I've stuffed "default" in the title above. If someone wants to suggest a better (i.e. more accurate and neutral) title, we can change it again.
Earlier quoted context omitted.
>They could just have operators translate the configs automatically on the fly How do they test that across the infinite number of permutations of configurations and deployments of K8S in the field though? It'll work for some people on the happy path, but it's really hard to maintain over time. Worse, it'll break randomly at some point in the future that is hard to predict, instead of at some publicly announced point…
I don't know any software library that introduces breaking changes as often as kubernetes does. Devops used to be leaning more to stability then devs, it's weird. Kubernetes devops are very expensive so I guess they love being able to spend more time on their tool
I tried k3s several times in the past few years but I still can't use it in my homelab: 1. the project claims to be production ready and support HA control plane setup, but there's no solution for API load balancing out of box. How do you bring up a new node(either control plane or worker node)? You write down the join token produced by the first control plane node, and hardcode the token and the existing control pla…
> but there's no solution for API load balancing out of box Why do you need this in a homelab?
1. My homelab has a lot of crappy hardware with zero enterprise support. And when a server fails, I need to be able to easily swap it out. And I don't want to make it a full time job for myself to maintain it.
2. I did knock some control plane nodes down a few times. It was rare, but still not fun.
3. Also, because why not? HA control plane is not particularly challenging these days. I know exactly how to do it. I just don't have the bandwidth to learn how to do it in k3s, especially when it comes for free in some other distributions.
hmmmmm no mention of pvcs eh
Just make sure to remember to set it as the default storage class.
Earlier quoted context omitted.
"vanilla kubernetes" isn't a distribution either. > Kubernetes and k3s are both container orchestration platforms Your article makes it seem like k3s and k8s are different platforms which is simply incorrect. A more useful comparison would have been to compare k3s with another distribution like EKS, GKE, OKD etc.
i kindly ask again, what is the distribution called that you setup with kubeadm?