Traefik can listen on individual addresses on a machine, which lowers the barrier to making a chained ingress. If chained ingress doesn't make sense, think of h

Traefik can listen on individual addresses on a machine, which lowers the barrier to making a chained ingress. If chained ingress doesn't make sense, think of how Kubernetes has a load balancer pointing at several nodes and each of those nodes run an ingress internally to route traffic across the private-to-the-node network. For instance, I didn't want my sharing URLs to enter directly on my home IP. I felt that would expose my house to an enumeration of vectors that I couldn't possibly control. I ended up creating a small server in digital ocean that runs Traefik on a public address with various public DNS records pointing at it. That instance of Traefik then points to my home servers Tailscale addresses. I actually go a step further by running Traefik on each server so that I can host multiple services on port 443 on each server, but this isn't absolutely necessary. Hopefully that all made sense!