aigatewayroute
AIGatewayRoute combines multiple AIServiceBackends and attaching them to Gateway(s) resources. This serves as a way to define a "unified" AI API for a Gateway which allows downstream clients to use a single schema API to interact with multiple AI backends. Envoy AI Gateway will generate the following k8s resources corresponding to the AIGatewayRoute: - HTTPRoute of the Gateway API as a top-level resource to bind all backends. The name of the HTTPRoute is the same as the AIGatewayRoute. - HTTPRouteFilter of the Envoy Gateway API per namespace for automatic hostname rewrite. The name of the HTTPRouteFilter is `ai-eg-host-rewrite-${AIGatewayRoute.Name}`. All of these resources are created in the same namespace as the AIGatewayRoute. Note that this is the implementation detail subject to change. If you want to customize the default behavior of the Envoy AI Gateway, you can use these resources as a reference and create your own resources. Alternatively, you can use EnvoyPatchPolicy API of the Envoy Gateway to patch the generated resources. For example, you can configure the retry fallback behavior by attaching BackendTrafficPolicy API of Envoy Gateway to the generated HTTPRoute.
https://raw.githubusercontent.com/nlamirault/schema-hub/main/schemas/aigateway.envoyproxy.io/aigatewayroute_v1beta1.json▶Usage examples
# yaml-language-server: $schema=https://raw.githubusercontent.com/nlamirault/schema-hub/main/schemas/aigateway.envoyproxy.io/aigatewayroute_v1beta1.jsonkubeconform -schema-location 'https://raw.githubusercontent.com/nlamirault/schema-hub/main/schemas/{{ .Group }}/{{ .ResourceKind }}_{{ .ResourceAPIVersion }}.json' manifest.yamlResource Structure
apiVersionstringkindstringmetadataobjectspecobjectstatusobject