-
Notifications
You must be signed in to change notification settings - Fork 32
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
Comments
Consider utilizing Cilium Mesh with Isovalent Transit Gateway. Note: it's part of Isovalent Cilium Enterprise https://isovalent.com/blog/post/introducing-cilium-mesh/ Alternatively, there is Cilium VXLAN Tunnel Endpoint |
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. |
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. |
There are three systems:
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
The text was updated successfully, but these errors were encountered: