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
{{ message }}
Repository navigation
[docs] How to interconnect tenant with external systems via VXLAN #29
Users can have isolated VPC network between OpenNebula and Bare Metal servers delivered using VXLAN technology.
We need to describe how to deliver such VLXANs on Cozystack.
User stories
I have Kubernetes cluster in Cozystack and database that runs in VPS on OpenNebula, I want to connect my database from Kubernetes cluster over the private network.
I want to access my Kubernetes services from my VPS over the private network
changed the title [-]How to interconnect tenant with external systems via VXLAN[/-][+][kube-ovn] How to interconnect tenant with external systems via VXLAN[/+]on Mar 13, 2024
changed the title [-][kube-ovn] How to interconnect tenant with external systems via VXLAN[/-][+][networking] How to interconnect tenant with external systems via VXLAN[/+]on Mar 13, 2024
changed the title [-][networking] How to interconnect tenant with external systems via VXLAN[/-][+][docs] How to interconnect tenant with external systems via VXLAN[/+]on Mar 13, 2024
Consider utilizing Cilium Mesh with Isovalent Transit Gateway.
To make this work, install Transit Gateway next to the DB that attracts network traffic and redirects it into your k8s with Cilium.
If the k8s and the DB are located in two different DCs not connected via VXLAN, you may consider using two routers connected via VPN, one next to the DB and the other in the same network with k8s.
Alternatively, there is Cilium VXLAN Tunnel Endpoint
I think it good point. I will only expand the your idea - you can select the nodes like "router" which would work for interconnect amd entry point for other clusters and environments
Decided that providing services without encryption on public addresses is not secure. Therefore, it is assumed that the user will access their services from their own Kubernetes cluster or virtual machines. If they need to access their services from outside, they can still use their own VPN server, set up in their namespace.
Activity
[-]How to interconnect tenant with external systems via VXLAN[/-][+][kube-ovn] How to interconnect tenant with external systems via VXLAN[/+][-][kube-ovn] How to interconnect tenant with external systems via VXLAN[/-][+][networking] How to interconnect tenant with external systems via VXLAN[/+][-][networking] How to interconnect tenant with external systems via VXLAN[/-][+][docs] How to interconnect tenant with external systems via VXLAN[/+]qdrddr commentedon Mar 26, 2024
Consider utilizing Cilium Mesh with Isovalent Transit Gateway.
To make this work, install Transit Gateway next to the DB that attracts network traffic and redirects it into your k8s with Cilium.
Note: it's part of Isovalent Cilium Enterprise
https://isovalent.com/blog/post/introducing-cilium-mesh/
Alternatively, there is Cilium VXLAN Tunnel Endpoint
https://docs.cilium.io/en/stable/network/vtep
qdrddr commentedon Mar 26, 2024
If the k8s and the DB are located in two different DCs not connected via VXLAN, you may consider using two routers connected via VPN, one next to the DB and the other in the same network with k8s.
Uburro commentedon Mar 27, 2024
I think it good point. I will only expand the your idea - you can select the nodes like "router" which would work for interconnect amd entry point for other clusters and environments
kvaps commentedon Apr 26, 2024
Decided that providing services without encryption on public addresses is not secure. Therefore, it is assumed that the user will access their services from their own Kubernetes cluster or virtual machines. If they need to access their services from outside, they can still use their own VPN server, set up in their namespace.
kvaps commentedon Mar 25, 2025
Initially solved by cozystack/website#102