Transit needs citizen traffic for host schedules.city.example to reach the schedules Service through an existing Gateway listener. Which Gateway API action is correct?
Select an answer to reveal the explanation.
Short Explanation
The Gateway is the curb cut; the HTTPRoute is the street sign that says “schedules.city.example goes to this Service.” Match the host, attach to the listener, and point the backend at the Service—not a bare Pod IP.
Full Explanation
HTTPRoutes match hosts and paths and attach to Gateway listeners that accept them. Backends are typically Services, so the route stays stable as Pods churn. Renaming Gateways, annotating Pods, or pointing DNS at ephemeral Pod IPs does not implement Gateway API host-based routing.