From f306e1df10cd531f415f82f0016fc237ec2a8ea0 Mon Sep 17 00:00:00 2001 From: as51340 Date: Tue, 14 Jul 2026 12:55:13 +0200 Subject: [PATCH] fix: Update TCPRoute to use GA channel --- pages/clustering/high-availability/setup-ha-cluster-k8s.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pages/clustering/high-availability/setup-ha-cluster-k8s.mdx b/pages/clustering/high-availability/setup-ha-cluster-k8s.mdx index 7cfd0ef69..333f6b531 100644 --- a/pages/clustering/high-availability/setup-ha-cluster-k8s.mdx +++ b/pages/clustering/high-availability/setup-ha-cluster-k8s.mdx @@ -691,7 +691,7 @@ externalAccessConfig: The chart will create: - A **Gateway** (`gateway.networking.k8s.io/v1`) with TCP listeners auto-generated for each data and coordinator instance. -- A **TCPRoute** (`gateway.networking.k8s.io/v1alpha2`) per instance, routing traffic from the Gateway listener to the instance's Bolt port. +- A **TCPRoute** (`gateway.networking.k8s.io/v1`) per instance, routing traffic from the Gateway listener to the instance's Bolt port. Data instance ports are assigned as `dataPortBase + array index` (default: 9000, 9001, ...) and coordinator ports as `coordinatorPortBase + coordinator id` (default: 9011, 9012, 9013). You can customize the base ports: @@ -773,7 +773,7 @@ A standalone Gateway manifest with these pre-configured listeners is available i -**TCPRoute API version**: TCPRoute uses `v1alpha2`, which is the latest available API version. It is supported by Envoy Gateway and other major implementations but is not yet GA. Gateway and HTTPRoute are both GA (`v1`). +**TCPRoute API version**: TCPRoute uses `v1`, which is the latest available API version. It is supported by Envoy Gateway and other major implementations but is not yet GA. Gateway and HTTPRoute are both GA (`v1`). ### Use Memgraph HA chart with IngressNginx