Network to Other Selectel Services

Network to Dedicated Servers

An L3VPN network, which is used to network a Managed Kubernetes cluster with dedicated servers, is created upon request. The L3VPN network to dedicated servers does not have access to the Internet — it needs to be configured. In a Managed Kubernetes cluster, Internet access is required to install packages on nodes and to retrieve metadata from OpenStack.

Follow these steps to establish connectivity between Managed Kubernetes and dedicated servers:

  1. To connect an L3VPN network, submit a request on the Private Networks tab of the Cloud platform — Networks Services section in the Control panel.
  2. Create a router in the Control panel or through the OpenStack CLI. Learn more about managing networks.
  3. Connect the router to the external-network.
  4. Connect the router to the created L3VPN network. When connecting the router, the IP address of the port is assigned.
  5. Change the default gateway from the L3VPN router to the newly created one. Use the IP address from the previous step:

    openstack subnet set --gateway <IP_address> <subnet_UUID>
  6. Add the required static routes to connect to dedicated servers:

    openstack subnet set --host-route destination=<dedicated_subnet>,gateway=<hardware_router_IP> <subnet_UUID>
  7. Create a cluster by selecting the L3VPN network created upon request.

Example of a Typical Solution

You need to connect your Managed Kubernetes cluster with dedicated servers. The following subnets are used to establish L3VPN connectivity:

  • 192.168.0.0/24 for Managed Kubernetes;
  • 192.168.1.0/24 for Dedicated servers;
  • 192.168.0.254 for the Cloud platform as a gw L3VPN router, 192.168.0.252 - 192.168.0.253 — reserved for VRRP.

In this case, the commands will look as follows.

Changing the default gateway from the L3VPN router to the OpenStack router:

openstack subnet set --gateway 192.168.0.1 <subnet_UUID>

Adding static routes:

openstack subnet set --host-route destination=192.168.1.0/24,gateway=192.168.0.254 <subnet_UUID>

Network to Cloud Servers

Within One Project

If the Managed Kubernetes cluster and Cloud platform virtual machines are in the same project and need to be connected, then follow these steps in the Control panel:

  1. Create a private network.
  2. Connect the network to the router.
  3. When creating a Managed Kubernetes cluster, select the created private network.
  4. Add virtual machines to the network.

Between Projects

If the cluster and cloud servers are in different projects, you need to make the private network of one project available to another project — such a network is called cross-project.

To do this, from the Control panel:

  1. Create a private network in the current project.
  2. Connect the network to the router.
  3. When creating a Managed Kubernetes cluster, select the created private network.
  4. Make your private network cross-project.
  5. Add virtual machines to the cross-project network in the target project.

Network to DBaaS

A Managed Kubernetes cluster and a Managed Databases cluster are networked in the same way as networking with cloud servers — in one project and between projects.