awesome-home-kubernetes VS homelab

Also check out the awesome kubernetes@home repo where many homelabbers share their configs.

Sorry I'm not familiar with this. Are you referring to this?

https://github.com/k8s-at-home/awesome-home-kubernetes https://github.com/k8s-at-home/template-cluster-k3s

To see it in action be sure to check out my repository or the many others here.

Make it usable and link to the best place with k3s in action: https://github.com/k8s-at-home/awesome-home-kubernetes

Nice but I suggest going to https://github.com/k8s-at-home/awesome-home-kubernetes and learn from the best at this topic ;)

Check out Flux V2. It syncs a git repo with your cluster, allowing you to define your infrastructure as code. It will keep your cluster synced with your repo and detect changes. A number of example repos are Here and onedr0p did a example repo here There's many options for structuring folder, I'd recommend you have a look at a few repos and pick one you like. The linked template is a good start, as it helps avoid dependency hell with a crd folder that starts before the YAML that needs the crd defined. Many people on the awesome list also run ansible for full infrastructure as code. I spent a lot of time perfecting my setup to go from blank Ubuntu VM to my cluster with a few keystrokes. Running it in git also helps you be able to use things like renovate bot to keep versions up to date. As for namespaces, everyone had their own method, but about using kube-system. Also, keep a eye out for services that refuse to have their name space changed.

I do similar stuff but without windows https://gitlab.com/dekarl/homelab/-/blob/master/kubernetes-cluster.tf replace the maas stuff with hyperv

I do the configuration of my playground cluster like that. See https://gitlab.com/dekarl/homelab/-/tree/master/ (charts/configuration and helmfile-configuration)

My current homelab consists of amd64 thin clients, a NAS with MaaS and plain WiFi controlled power plugs. I'm still stuck at stateless workloads. Persistant volumes come after the Summer break.

I'm playing around with MaaS, too. Currently using microk8s, but looking for a replacement, like Talos.

Keeping the manifest updated should become a copypaste battle around now. Time to look into helmfile with one embedded chart for one handler and many instantiations. Start with one folder for the charts and two folders for the deployment to prod/stage. I started such a setup for my homelab at https://gitlab.com/dekarl/homelab/-/tree/master/