kube-config VS microk8s

Helm is an absolute mess in my experience.

I'm using zigbee2mqtt in K8s and just pinning the deployment to a node and mapping the device as a volume: https://github.com/LukeChannings/kube-config/blob/3b61c7607c...

Should work the same for Home Assistant, but I don't use HA for Zigbee directly, instead using z2m -> MQTT -> HA, which I've found to be very robust.

I'm waiting for a new K8s cluster (based on CM4) and when I re-implement all of this I'll get a network-based PoE Zigbee device (https://smlight.tech/manual/slzb-06/), that way I can un-pin the deployment and look at high availability Zigbee via MQTT (something Home Assistant doesn't support)

I run ArgoCD (which has been great), and keep all of my definitions (and encrypted secrets) in a public GitHub repo.

Now I run k3s and use Argocd + git and everything is great, honestly. https://github.com/LukeChannings/kube-config

If you want hands-on practice you should have a running Kubernetes cluster (I used MicroK8s for this tutorial) and Helm (see how to install on Installing Helm tutorial). It is important that you understand the basics of these tools to fully understand.

And install microk8s:

MicroK8s is a lightweight, batteries included Kubernetes distribution by Canonical designed for running edge workloads which also happens to be developer-friendly and a great choice for building your own homelab. The following lab covers how to install and run MicroK8s on your own edge node running Ubuntu 22.04 LTS, deploy the NGINX web service and exposing your NGINX website to the Internet with SSL/TLS enabled using AWS resources included within the Free Tier.

One quick and easy win I can recommend, is microk8s.

I had the same problem (and there's a github issue about this: https://github.com/canonical/microk8s/issues/2186). I swapped to k3s and the usage was half of what microk8s used.

microk8s currently has a showstopping issue that makes it guaranteed to have an irrecoverable failure in HA mode. see https://github.com/canonical/microk8s/issues/3227

k0s is better but also has a lot of bugs. it's the closest to vanilla kubernetes among all the distributions.

> like the simplest GPU support

linux users should be ready to install the nvidia device plugin. if they can't do that, they're never going to succeed in running a gpu accelerated application on their cluster anyway.

> like bootstrapping

in my experience, writing all the bootstrap scripts is painful. but now that there's chatgpt, so much of the drudgery as gone away.

MicroK8S to spin up a Kubernetes cluster

They now power my microk8s/x86 cluster (in addition to my 8-node Raspberry Pi4 ARM64 microk8s cluster), microceph cluster and my LXD cluster, and all are configured with WOL, so I can bring up the cluster from any machine in the homelab, on demand.