Apply a Gateway, an HTTPRoute and a Certificate, then watch three controllers turn that YAML into a load balancer, DNS records in Route 53 and a Let's Encrypt certificate proven with a DNS-01 challenge. Split traffic by weight and header, age the certificate, break an IAM permission, or press ▶ Guided tour.
Controllers connect Kubernetes objects to the world outside the cluster. A Gateway controller turns a Gateway into a load balancer. external-dns reads hostnames from routes and writes DNS records, with a TXT record so it only deletes what it owns. cert-manager turns a Certificate into a real certificate through ACME: it publishes a challenge, the CA checks it, and the result lands in a Secret the listener reads, renewed automatically at two thirds of its life. Gateway API splits what Ingress kept in one object: the GatewayClass belongs to the infrastructure team, the Gateway to the platform team, and HTTPRoutes to app teams, with weights and header matches built in.