The next gitops task for my home cluster was to make ArgoCD automatically install new applications when I add them to the configuration git repository. In this post, I’m going to show how to set up an Argo CD git generator ApplicationSet and point it at a specific directory in a configuration repository. ...
Now that the cluster is up and has Argo CD controlling application deployment, I’m starting to move my homelab services out of docker-compose stacks and into my k8s cluster. I run MQTT (Eclipse Mosquitto in my case) as a message bus between zigbee2mqtt, zwave-js-ui and Home Assistant, so it’s the first service I’m moving into the k8s cluster. ...
In part five of my kubernetes homelab series, we will install Argo CD into a homelab cluster so we can use gitops practices instead of ad-hoc kubectl commands. This will make it much easier to recreate the cluster exactly if we decide to move it to new hardware or just want to reset things to a known-good state after experimentation. Part 1 - Setting up Talos with a Cilium CNI on proxmox Part 2 Add SSL to Kubernetes using Cilium, cert-manager and LetsEncrypt with domains hosted on Amazon Route 53 Part 3 - Secret Management with SOPS Part 4 - Back up your Talos etcd cluster to a SMB share Part 5 - Install Argo CD Part 6 - Install MQTT into a k8s cluster Part 7 - Add an ArgoCD git generator ApplicationSet Why bother with gitops? It’s a homelab, and I’m the only administrator Using gitops to configure your cluster instead of running kubectl apply commands directly makes it possible to reproduce the exact state of the cluster later if you need to revert to a known-good state. ...