You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(outbound): Use the policy API for opaq routing (#3306)
The OutboundPolicy API is able to express configuration for opaq routing, but
the proxy only currently uses the ServiceProfile to configure routing. To
support configuring routing via the Gateway API's TCPRoute, we need to begin
using the OutboundPolicy API to configure opaq routing without breaking
existing configurations that use profiles.
With this change, the outbound proxy is updated so that route configurations are
required for the proxy to handle outbound opaq traffic. Route configurations may
be provided by:
* The Profile API, when it returns an Endpoint, so that the proxy synthesizes a
route configuration that forwards traffic to the endpoint.
* The Profile API, when it returns a traffic split configuration, so that the
proxy synthesizes a route configuration that forwards traffic over backend
services.
* The OutboundPolicy API when it returns opaq routes.
When no routes are returned by the API, the proxy fails to route the
connections.
Follow up changes will enhance this functionality with metrics and improved
metadata.
0 commit comments