v1alpha1 has been deprecated
Please upgrade to v1alpha2, v1alpha1 will be removed from Gateway API in an upcoming release.
Gateway API is designed to work with multiple protocols. TCPRoute is one such route which allows for managing TCP traffic.
In this example, we have one Gateway resource and two TCPRoute resources that distribute the traffic with the following rules:
- All TCP streams on port 8080 of the Gateway are forwarded to port 6000 of
- All TCP streams on port 8090 of the Gateway are forwarded to port 6000 of
Please note the following:
protocolof listeners on the Gateway is
- Each listener selects exactly one TCPRoute. This is important since the routing
decision is performed based on destination port only. If more metadata is used
for routing decisions, then one may associate multiple TCPRoutes to a single
Gateway listener. Implementations can support such use-cases by adding a custom
resource to specify advanced routing properties and then referencing it in
spec.rules.matches.extensionRef. Conflicts due to routing colisions should be resolved as per the conflict resolution guidelines.
apiVersion: networking.x-k8s.io/v1alpha1 kind: GatewayClass metadata: name: acme-lb spec: controller: acme.io/gateway-controller parametersRef: name: acme-lb group: acme.io kind: Parameters --- apiVersion: networking.x-k8s.io/v1alpha1 kind: Gateway metadata: name: my-tcp-gateway spec: gatewayClassName: acme-lb listeners: - protocol: TCP port: 8080 routes: kind: TCPRoute selector: matchLabels: "app": "foo" - protocol: TCP port: 8090 routes: kind: TCPRoute selector: matchLabels: "app": "bar" --- apiVersion: networking.x-k8s.io/v1alpha1 kind: TCPRoute metadata: name: tcp-app-1 labels: app: foo spec: rules: - forwardTo: - serviceName: my-foo-service port: 6000 --- apiVersion: networking.x-k8s.io/v1alpha1 kind: TCPRoute metadata: name: tcp-app-2 namespace: default labels: app: bar spec: rules: - forwardTo: - serviceName: my-bar-service port: 6000