Retiring ingress-nginx from a Talos Kubernetes Homelab: Envoy Gateway as the Only Front Door

Overview

The public tier already lives on the Gateway, and the private routes and the Factorio lane are in place but dormant behind ingress-nginx. This article opens with the one cutover that activates them, the private wildcard record moving to the Gateway's address, and once that is verified ingress-nginx serves nothing. Then it removes it: the Ingress objects that were the rollback path, the controller with its namespace and policy, the two wildcard Certificates it held, and the reflector that existed only to mirror those certificates. The address it held returns to the MetalLB pool.