In this video I continue my Kubernetes homelab adventure—after getting the cluster up, adding Longhorn for storage, and using MetalLB for load balancing, I finally set up Traefik for routing. The big win with Traefik is I don’t need a giant pool of IPs for every service anymore. I can point DNS at a single MetalLB external IP and let Traefik do host-based routing (name-based routing) to the right service. I walk through deploying Traefik via Helm, including adding the Traefik Helm repo, pulling the chart, and tweaking values.yaml so the service grabs the exact MetalLB IP I want. Then I show how I expose an app (Uptime Kuma) using an IngressRoute on the websecure entrypoint and lock it down with TLS using my self-signed wildcard cert (via step-ca). The key takeaway: your TLS secret has to live in the same namespace as the app you’re routing to, even if it’s the same wildcard cert. Once Traefik is installed, it’s basically rinse-and-repeat—create a secret in the namespace, apply an IngressRoute, and you’re done.