The Gateway API is Ingress's successor and divides the work by role. A GatewayClass names the controller. The platform team creates a Gateway, which owns the listeners (ports, protocols, host names) and says which namespaces may attach routes. Application teams create HTTPRoutes in their own namespaces and attach them to a Gateway with parentRefs.
An HTTPRoute lists hostnames and rules. Each rule can match paths, headers or query parameters, and sends traffic to backendRefs: Services with their port and an optional weight. Weights split one rule's traffic between backends, which is how a canary gets 10% of requests; matches send whole requests to a rule by what they contain.
parentRefs look in the route's own namespace unless you add namespace. When a route doesn't work, read its status: Accepted says whether a Gateway took it, ResolvedRefs whether its backends exist.
A route on a shared Gateway with a 10% canary.