Reference

This page describes the Gateway and Vendor extension resources.

API Resources

With Gateway for Mesh an xRoute typically uses a Kubernetes Service as theparentRef. When usedthis way, the parent Service becomes the "service frontend" for the client tocall where the service gets an automatically allocated DNS name(name.namespace.svc.cluster.local) and IP address (ClusterIP). A proxylessgRPC 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 usersto specify fine-grained routing rules for HTTP traffic - based on attributeslike hostnames, paths, headers, and methods, determine how requests are directedwithin the cluster. HTTPRoute can also be attached to Gateways, which act asentry points for traffic into the cluster.

For more information, seeHTTPRoute.

GRPCRoute

The GRPCRoute API specification is part of the Kubernetes Gateway API anddefines a resource for routing gRPC traffic within a Kubernetes cluster. Itlets users specify how gRPC requests should be matched and directed to backendservices based on criteria like hostnames, gRPC methods, and headers. You canalso attach GRPCRoutes to Gateways which act as entry points for traffic intothe cluster. This specification enables fine-grained control over gRPC trafficrouting, making it a valuable tool for managing gRPC-based applications inKubernetes.

For more information, seeGRPCRoute.