Gateway Routes with conflicting Services in their backend should not break config build #2565
Labels
area/gateway-api
Relating to upstream Kubernetes SIG Networking Gateway API
bug
Something isn't working
size/medium
Milestone
If service population fails due to a single Gateway Route using multiple Services whose annotation sets differ, that failure bubbles up to the parser build and indicates that it failed completely, and the parser build bubbles that up saying that it also failed completely. This blocks the entire config build because of one misconfigured Route.
We should be able to only break the Route in question and skip it, proceeding with the rest of the config. Roughly, this would require logging the failure, adding some entry to
ingressRules.ServiceNameToServices
that we can recognize as a failure, and then later skipping/logging the route using that service (or the service, forget offhand which we have at the top of the Kong config tree) when building the larger config.Acceptance:
The text was updated successfully, but these errors were encountered: