Mauricio Teixeira🐧Dec 4

"Kubernetes is overkill for a Home Lab", exhibit 493 (made up number): I'm trying to make Pi-Hole egress to the internet via the loadbalancer IP, rather than the node IP (default). To do that, I need to implement Cilium Egress Gateway, which is horribly complicated, and will be used for a one-off. But if I don't do so, I need to review all my firewall rules, which only allow very few IP addresses in my network to query external DNS servers. Ugh. I'm starting to reconsider my sanity. What am I getting myself into?  

Edit: nothing like a good night of sleep. I found a solution using traffic policies in my router, so I no longer need the complexity of the k8s egress gateway. 👍

#HomeLab #TalosLinux #Kubernetes #Cilium #PiHole @homelab

Show threadKrist van Besien
@badnetmask @homelab
Would Nomad for a homelab be an option? I have a TuringPI box, with 4 nodes, and need something to orchestrate that. Have been playing around with kubernetes. Nomad looks interesting.
Dec 4 at 5:20amWeb
Show threadGizDec 4
@krist @badnetmask @homelab
Certainly, Nomad works great. I'm using it with consul on my homelab.
Show threadKrist van BesienDec 4
@Giz @badnetmask @homelab currently my plan is to use bootc to create fedora images with nomad and consul installed, then configure using ansible, and the have fun with nomad.
Show threadUrsi38Dec 4
@krist @badnetmask @homelab
Nomad is nice and works well.
My personal journey was k8s, k3s, Nomad and now basic docker-compose managed with Komodo & Forgejo (auto deploy with webhook on git push). 3 HW machines, several VMs.
Show threadMauricio Teixeira🐧Dec 4
@abmurksi @krist @homelab
Nomad not only is too narrow of a (weird) niche, but is also basically vendor lock-in. I know a few people who migrated from Nomad to some Kubernetes distro. Certainly not a choice for me.
Show threadUrsi38Dec 4
@badnetmask @krist @homelab
Fair, especially the vendor lock-in is real.
But for workload orchestration it worked well.