I found that the biggest blocker to running Kubernetes locally is that it's very resource-hungry, especially on a Mac with Linux virtualization. This also true

I found that the biggest blocker to running Kubernetes locally is that it's very resource-hungry, especially on a Mac with Linux virtualization. This also true about Docker on Mac, but Kubernetes is worse. I have not tried k3s or any of the other attempts to produce a stripped-down version, so I'm curious if they fix this problem. But the fact remains that the Kubernetes daemons are heavily based on polling; even a Kubernetes instance that does nothing will be using a lot of CPU. Right now, the tool of my dreams does not run anything locally at all, but transparently maintains a small remote Kubernetes cluster in the cloud of my choice. The benefit here is that I could get all the tools at my disposal, such as public load balancers, ability to effortlessly scale up my nodes when needed, etc.