From 6d6f5701c1df8bdd330dd7b84d8185fcbe0cea01 Mon Sep 17 00:00:00 2001 From: jinwhu <88138777+jinwhu@users.noreply.github.com> Date: Fri, 31 Oct 2025 15:15:32 +0800 Subject: [PATCH] Update set-up-vpc-peering-connections.md remove dedicated gcp cidr 16-18 feature control --- tidb-cloud/set-up-vpc-peering-connections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/set-up-vpc-peering-connections.md b/tidb-cloud/set-up-vpc-peering-connections.md index 5fbc8bf4f3fe0..87259ad7c34d1 100644 --- a/tidb-cloud/set-up-vpc-peering-connections.md +++ b/tidb-cloud/set-up-vpc-peering-connections.md @@ -41,7 +41,7 @@ You can set the CIDR when creating the first TiDB Cloud Dedicated cluster. If yo > - 10.250.0.0 - 10.251.255.255 > - 172.16.0.0 - 172.31.255.255 > - 192.168.0.0 - 192.168.255.255 - > - For Google Cloud Region, it is recommended to configure an IP range size between `/19` and `/20`. If you want to configure an IP range size between `/16` and `/18`, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md). Supported network addresses include: + > - For Google Cloud Region, it is recommended to configure an IP range size between `/19` and `/20`. Supported network addresses include: > - 10.250.0.0 - 10.251.255.255 > - 172.16.0.0 - 172.17.255.255 > - 172.30.0.0 - 172.31.255.255