k8s02 podcidr # K8S Service CIDR, not overlap with node(host) networking
SERVICE_CIDR="10.62.0.0/16"

Cluster CIDR (Pod CIDR), not overlap with node(host) networking

CLUSTER_CIDR="172.22.0.0/16"

NodePort Range

NODE_PORT_RANGE="30000-32767"

k8s03 podcidr# K8S Service CIDR, not overlap with node(host) networking
SERVICE_CIDR="10.63.0.0/16"

Cluster CIDR (Pod CIDR), not overlap with node(host) networking

CLUSTER_CIDR="172.23.0.0/16"

NodePort Range

NODE_PORT_RANGE="30000-32767"

Cluster DNS Domain

CLUSTER_DNS_DOMAIN="cluster.local"

cilium cidr with helm---k8snode02
ipam:

-- Configure IP Address Management mode.

ref: https://docs.cilium.io/en/stable/network/concepts/ipam/

mode: "cluster-pool"

-- Maximum rate at which the CiliumNode custom resource is updated.

ciliumNodeUpdateRate: "15s"
operator:
# -- IPv4 CIDR list range to delegate to individual nodes for IPAM.
clusterPoolIPv4PodCIDRList: ["172.0.0.0/8"]

ipv4NativeRoutingCIDR: "172.0.0.0/8"

k8snode03 is the same

by the way,ihave tested differernt podcidr 3times

from cilium.

Hi @15927561940,

The error is that the node in the first cluster cannot access the clustermesh-apiserver in the second one:

- https://cluster3.mesh.cilium.io:2379
     ✅ Hostname resolved to: 172.25.80.200
     ❌ Cannot establish TCP connection to cluster3.mesh.cilium.io:2379: dial tcp 172.25.80.200:2379: i/o timeout

This typically indicates issues in the underlying VPC or security groups configuration, or in the LoadBalancer settings. I'd suggest trying to ssh into the node and verifying that you can correctly curl 172.25.80.200:2379, as well as that the clustermesh-apiserver pod is correctly up and running in both clusters.

from cilium.