You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In situations where there are multiple Kubernetes clusters in existence, the cluster networks often conflict with each other. If a cross-cluster service needs to be deployed across multiple existing clusters, in the case of network segment conflicts, we can create a new ip pool that does not conflict. The pod-ip of the newly created pod will use the new ip pool address range, and the container networks between the new ip pools will be interconnected through clusterlink.
The text was updated successfully, but these errors were encountered:
In situations where there are multiple Kubernetes clusters in existence, the cluster networks often conflict with each other. If a cross-cluster service needs to be deployed across multiple existing clusters, in the case of network segment conflicts, we can create a new ip pool that does not conflict. The pod-ip of the newly created pod will use the new ip pool address range, and the container networks between the new ip pools will be interconnected through clusterlink.
The text was updated successfully, but these errors were encountered: