Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another solution to cluster network segment conflict for clusterlink #620

Open
duanmengkk opened this issue Jun 4, 2024 · 0 comments
Open

Comments

@duanmengkk
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant