Feature: Implement Custom Topology Definition for a Slice
🔖 Feature description
KubeSlice currently uses a full-mesh topology for the slice overlay network, where every cluster connects to every other cluster in the slice. This results in unnecessary tunnel creation and resource consumption.
🎤 Pitch
This project proposes a topology-aware design, allowing users to define custom connectivity matrices for slices. Users can specify partial meshes. Additionally, the project will support configuring each cluster's VPN deployment type (client/server) to accommodate network constraints such as firewalls or NAT.
✌️ Solution
- Extension of the Slice CRD to support custom topology and VPN role definitions.
- Logic to establish tunnels based only on the defined connectivity matrix.
- Support for various deployment topologies (full-mesh, partial mesh, hub-spoke).
- Sample configurations and documentation on how to define and validate topologies.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
- [x] I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- [x] I have read the Code of Conduct
Hello maintainers , @narmidm @priyank-upadhyay @richiesebastian This is Ronak . I had this question which will clarify my doubt as well as doubts of many others and avoid useless comments:
Is there any PRE-TEST to be conducted/ The number of contributions / The proposal holds the utmost power for SELECTION. Thank You.. would love to be a part of kube-slice .
Hey Folks, this project is under LFX Mentorship program, Please use the LFX website to apply and learn more at https://mentorship.lfx.linuxfoundation.org/project/db7a4bc3-3489-4ca9-9d6a-13f27fbee7fc
If you want to look at some good first issues and participate in Kubeslice development please take a look at https://github.com/orgs/kubeslice/projects/4
Hey @RONAK-AI647 we are looking for contributors who understand kubeslice, networking and IPAM for this project, you can apply through the LFX Mentorship program with a cover letter describing your expertise.
I would encourage you to go over the issues in kubeslice org https://github.com/orgs/kubeslice/projects/4 and see both open and closed issues in the repos to understand the active fields of contribution.
For hands on experience with kubeslice and understanding the product please take a look at the official docs at https://kubeslice.io/
Hi @gourishkb
Is there a defined roadmap or timeline for implementing the topology-aware networking feature?