Skip to content

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

Description

@kvaps

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

Activity

  1. 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
  2. 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
  3. 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
  4. added this to the milestone on Mar 13, 2024
  5. qdrddr commented on Mar 26, 2024

    @qdrddr

    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

  6. qdrddr commented on Mar 26, 2024

    @qdrddr

    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.

  7. Uburro commented on Mar 27, 2024

    @Uburro

    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

  8. kvaps commented on Apr 26, 2024

    @kvaps
    MemberAuthor

    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.

  9. removed this from the milestone on Aug 6, 2024
  10. kvaps commented on Mar 25, 2025

    @kvaps
    MemberAuthor

    Initially solved by cozystack/website#102

  11. moved this from In progress to Done in Cozystackon Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions