Reference

Preview

This product or feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products and features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

This page describes the Gateway and Vendor extension resources.

API Resources

With Gateway for Mesh an xRoute typically uses a Kubernetes Service as the parentRef. When used this way, the parent Service becomes the "service frontend" for the client to call where the service gets an automatically allocated DNS name (name.namespace.svc.cluster.local) and IP address (ClusterIP). A proxyless gRPC client then uses the channel URI to access the service at

xds:///SERVICE_NAME.NAMESPACE_NAME.svc.cluster.local:${PORT}

HTTPRoute

The HTTPRoute API specification, a key component of the Kubernetes Gateway API, defines a resource for routing HTTP traffic within Kubernetes. It allows users to specify fine-grained routing rules for HTTP traffic - based on attributes like hostnames, paths, headers, and methods, determine how requests are directed within the cluster. HTTPRoute can also be attached to Gateways, which act as entry points for traffic into the cluster.

For more information, see HTTPRoute.

GRPCRoute

The GRPCRoute API specification is part of the Kubernetes Gateway API and defines a resource for routing gRPC traffic within a Kubernetes cluster. It lets users specify how gRPC requests should be matched and directed to backend services based on criteria like hostnames, gRPC methods, and headers. You can also attach GRPCRoutes to Gateways which act as entry points for traffic into the cluster. This specification enables fine-grained control over gRPC traffic routing, making it a valuable tool for managing gRPC-based applications in Kubernetes.

For more information, see GRPCRoute.