What does k3k stand for? Can we just put whatever number we want between 2 letters now?
I suspect it’s ‘kubernetes in kubernetes’
K3k: Kubernetes in Kubernetes
11–20 of 55 posts
Re: K3k: Kubernetes in Kubernetes
#12What does k3k stand for? Can we just put whatever number we want between 2 letters now?
I suspect it's a play on another kubernetes variant, `k3s` ?
Re: K3k: Kubernetes in Kubernetes
#13I don’t understand how they are separating security in the virtual mode as they only mention pods. It seems every workload still shares the underlying node, even when in virtual mode.
Take for example the OCI cache on the nodes. What about cache poisoning?
Re: K3k: Kubernetes in Kubernetes
#14What does k3k stand for? Can we just put whatever number we want between 2 letters now?
k in k
Re: K3k: Kubernetes in Kubernetes
#15Do Rancher side products generally make it into a stable state such that you would want to run mission-critical systems on?
RKE (their Kubernetes deployment and management platform, mostly for various flavours of self managed environments) is pretty popular with the self-managed crowd that needs something to manage their on Orem Kubernetes clusters.
Re: K3k: Kubernetes in Kubernetes
#16Do Rancher side products generally make it into a stable state such that you would want to run mission-critical systems on?
(Former employee) They tend to either get enough traction very quickly and be supported for years, or not and be abandoned in weeks/months.
Re: K3k: Kubernetes in Kubernetes
#17What does k3k stand for? Can we just put whatever number we want between 2 letters now?
Disclosure as I am working for SUSE on Rancher.
It's Kubernetes in Kubernetes and a reference in k3s which is also a project we are heavily contributing to, at SUSE.
Re: K3k: Kubernetes in Kubernetes
#18I don’t understand how they are separating security in the virtual mode as they only mention pods. It seems every workload still shares the underlying node, even when in virtual mode. Take for example the OCI cache on the nodes. What about cache poisoning?
Aren't OCI caches content addressed?
Re: K3k: Kubernetes in Kubernetes
#19This type of approach carries a significantly higher operational risk compared to operating multiple Kubernetes clusters on separate VMs or physical hardware. If you eventually update the main Kubernetes cluster that manages the virtual clusters and something goes wrong, you could potentially bring down your entire fleet of Kubernetes clusters all at once.
Re: K3k: Kubernetes in Kubernetes
#20Hi everyone! I’m one of the maintainers of K3k at SUSE.
It’s really exciting to see this on the front page. The project actually started during a SUSE Hackweek by my colleague Hussein. It was initially envisioned as a "Kubernetes version of k3d," but it evolved into something more ambitious and eventually became a real product. We’ve always been big believers in the power of open source. For the current default "shared" mode, we even experimented with Virtual Kubelet, another CNCF project, during our development process.
I’ll be hanging around the thread today, so if you have any questions about the history, the tech stack, or where we're headed next, feel free to ask!