-
Notifications
You must be signed in to change notification settings - Fork 30
Labels
Description
🔖 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?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Labels
Type
Projects
Status
No status