how is this working ? is this like cilium eBPF ?
KWOK: Kubernetes WithOut Kubelet
31–40 of 50 posts
Re: KWOK: Kubernetes WithOut Kubelet
#32One of the use cases mentioned here is testing. One should also look at kind [1]. It is light weight, a really good candidate to setup dev environments.
Re: KWOK: Kubernetes WithOut Kubelet
#33Slight tangent inspired by the premise, but why do EKS etc cap the number of pods and other resources on a node?
We try to enable our customers to start on 1 node and scale up at their discretion, but found we had to into all sorts of contortions to make that work. Likewise, k8s is resource hungry. We can run the docker compose version on a much smaller laptop wrt CPU & RAM.
Re: KWOK: Kubernetes WithOut Kubelet
#34One of the use cases mentioned here is testing. One should also look at kind [1]. It is light weight, a really good candidate to setup dev environments. [1] https://kind.sigs.k8s.io/
I also use k3d and k0s:
Re: KWOK: Kubernetes WithOut Kubelet
#35Slight tangent inspired by the premise, but why do EKS etc cap the number of pods and other resources on a node? We try to enable our customers to start on 1 node and scale up at their discretion, but found we had to into all sorts of contortions to make that work. Likewise, k8s is resource hungry. We can run the docker compose version on a much smaller laptop wrt CPU & RAM.
It's been a while since I've used EKS, but I seem to recall it's primarily based on the maximum ENIs the instance type supports.
Re: KWOK: Kubernetes WithOut Kubelet
#36One of the use cases mentioned here is testing. One should also look at kind [1]. It is light weight, a really good candidate to setup dev environments. [1] https://kind.sigs.k8s.io/
I wonder how big of an effort it would be for Apple to take some engineers and make Mac OS support kernel namespaces/cgroups that would bridge the gap between all of these cool container features Linux has that requires a virtual machine to recreate on Mac.
Re: KWOK: Kubernetes WithOut Kubelet
#37To what extent can I run kubernetes locally with this tool? I don’t need many k8s features and existing local k8s solutions always have a noticeable CPU usage. The docs don’t clearly communicate things like this. There are some projects that store data in k8s but can otherwise run locally. One can run those without a k8s cluster locally by using kubebrain with in memory storage: https://github.com/kubewharf/kubebrain
You can actually run the kubelet in standalone mode without etcd, controller-manager, scheduler or api-server. Simply drop any static pods manifests into /etc/kubernetes/manifests and the kubelet will launch pods for you. Remove them and kubelet will too. Fun fact this is how kubeadm bootstraps a control plane from "scratch"
Re: KWOK: Kubernetes WithOut Kubelet
#38One of the use cases mentioned here is testing. One should also look at kind [1]. It is light weight, a really good candidate to setup dev environments. [1] https://kind.sigs.k8s.io/
I wonder how big of an effort it would be for Apple to take some engineers and make Mac OS support kernel namespaces/cgroups that would bridge the gap between all of these cool container features Linux has that requires a virtual machine to recreate on Mac.
They should enable nested virtualization on M1/M2 first. As it stands now it's impossible to do anything with KVM without dual booting Asahi
Re: KWOK: Kubernetes WithOut Kubelet
#39Earlier quoted context omitted.
I wonder how big of an effort it would be for Apple to take some engineers and make Mac OS support kernel namespaces/cgroups that would bridge the gap between all of these cool container features Linux has that requires a virtual machine to recreate on Mac.
They should enable nested virtualization on M1/M2 first. As it stands now it's impossible to do anything with KVM without dual booting Asahi
Wait really? How does Docker macOS work on M1/M2? Or does it not?
Re: KWOK: Kubernetes WithOut Kubelet
#40Earlier quoted context omitted.
They should enable nested virtualization on M1/M2 first. As it stands now it's impossible to do anything with KVM without dual booting Asahi
Wait really? How does Docker macOS work on M1/M2? Or does it not?
Docker Desktop runs dockerd in a Linux VM with Apple's hypervisor framework. You can also run containers in a Linux VM with Parallels or VMware Fusion hypervisors, QEMU on macOS also uses HVF not KVM. But you can't run VMs inside those VMs as it stands today. This works fine on Intel Macs which means you can't experiment and use KVM - one of the killer features of Linux and things like https://kubevirt.io/ and firecracker. Or VMs running stuff like Proxmox TrueNAS or ESXi (all possible on Intel macs and every x86_64 CPU)