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

[docs] How to interconnect tenant with external systems via VXLAN #29

Open
kvaps opened this issue Feb 23, 2024 · 4 comments
Open

[docs] How to interconnect tenant with external systems via VXLAN #29

kvaps opened this issue Feb 23, 2024 · 4 comments
Assignees
Milestone

Comments

@kvaps
Copy link
Member

kvaps commented Feb 23, 2024

There are three systems:

  • VPS hosting based on OpenNebula
  • Bare Metal servers
  • Cozystack for Kubernetes and managed services

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
@kvaps kvaps self-assigned this Feb 23, 2024
@kvaps kvaps changed the title How to interconnect tenant with external systems via VXLAN [kube-ovn] How to interconnect tenant with external systems via VXLAN Mar 13, 2024
@kvaps kvaps changed the title [kube-ovn] How to interconnect tenant with external systems via VXLAN [networking] How to interconnect tenant with external systems via VXLAN Mar 13, 2024
@kvaps kvaps changed the title [networking] How to interconnect tenant with external systems via VXLAN [docs] How to interconnect tenant with external systems via VXLAN Mar 13, 2024
@kvaps kvaps added this to the v0.2.0 milestone Mar 13, 2024
@qdrddr
Copy link

qdrddr commented 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
Copy link

qdrddr commented 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
Copy link

Uburro commented Mar 27, 2024

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

@kvaps
Copy link
Member Author

kvaps commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In progress
Development

No branches or pull requests

4 participants