Skip to main content

Create a Managed Kubernetes cluster on a dedicated server

Last update:

You can create a Managed Kubernetes cluster with a group of nodes on a dedicated server.

Dedicated servers are used when needed:

  • consistently high performance;
  • increased privacy;
  • reserved capacity.

In Managed Kubernetes, you can use dedicated servers of an off-the-shelf configuration with a local port.

The dedicated server has already been assembled, mounted and connected to a private network at L3 level with Kubernetes Control Plane using a global router.

In one project and in one pool, you can create a maximum of 10 fault-tolerant clusters and 10 basic Managed Kubernetes clusters on dedicated servers.

Managed Kubernetes clusters on dedicated servers are in beta testing. Consider the limitations when selecting clusters on dedicated servers.

  1. Configure the cluster.
  2. Configure the node group.
  3. Set up automation.

1. Configure the cluster⁠

  1. In the dashboard, on the top menu, click Products and select Managed Kubernetes.

  2. Click Create Cluster.

  3. Enter a name for the cluster. The name will appear in the names of the cluster objects: node groups, nodes, balancers, networks, and disks. For example, if the cluster name is kelsie, the name of the node group would be kelsie-node-gdc8q and the boot disk would be kelsie-node-gdc8q-volume.

  4. Select the region and pool where the master nodes will reside. Once a cluster is created, the pool cannot be changed.

  5. Select the version of Kubernetes.

  6. Select the type of cluster:

    • fault-tolerant — Control Plane is placed on three master nodes that run on different hosts in different segments of the same pool. If one of the three master nodes is unavailable, Control Plane continues to run;
    • basic — Control Plane is hosted on a single master node that runs on a single host on a single pool segment. If the master node is unavailable, Control Plane will not run.

    Once a cluster is created, the cluster type cannot be changed.

  7. Optionally: to make the cluster available on private network and inaccessible from the Internet, check the Private kube API checkbox. By default the cluster is created in public network and it is automatically assigned public IP-address of kube API, accessible from the Internet. After cluster creation the type of access to kube API cannot be changed.

  8. Click Continue.

2. Configure the node group⁠

When you create a cluster, you can add only one node group. You can add additional node groups to an existing cluster.

  1. In the Server Type field, select Dedicated Server.

  2. Select the pool in which all worker nodes in the group will be located. The worker nodes must be in the same reachability zone as the master nodes. Once a cluster is created, the pool cannot be changed.

  3. Configure the configuration of worker nodes in the group:

    3.1 Click Select Configuration.

    3.2 Select a tariff plan.

    3.3 Select a ready-made dedicated server configuration.

    3.4 Press Select.

    Once the cluster is created, the node configuration cannot be changed.

  4. Configure the number of worker nodes:

    4.1 Open the Fixed tab.

    4.2 Specify the number of nodes. For fault-tolerant operation of system components it is recommended to have at least two working nodes in the cluster, nodes can be in different groups.

  5. Optional: To add node group labels, in the Labels field, click Add. Enter the label key and value. Click Add. Once the cluster is created, you cannot create new labels, modify existing labels, or delete labels.

  6. Optional: To add node group tints, in the Tints field, click Add. Enter the key and value of the taint. Select an effect:

    • NoSchedule — new pods will not be added and existing pods will continue to run;
    • PreferNoSchedule — new pods will be added if there are no other available slots in the cluster;
    • NoExecute — running pods without tolerations will be removed.

    Click Add.

    Once a cluster is created, you cannot create new teints, modify existing teints, or delete teints.

  7. Optional: In the Network block, in the Cloud Infrastructure Subnet field, specify the CIDR of the new subnet that will be used for communication between the master nodes and the service global router. The subnet must meet the conditions:

    • subnet must be private — belong to the range 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;;
    • the subnet size must be /24;
    • subnet must not overlap with the ranges 10.10.0.0/16, 10.222.0.0/16``, 10.250.0.0/16, 10.251.0.0/24, and 172.250.0.0/14. These ranges participate in the internal addressing of Managed Kubernetes.

    If you do not specify a CIDR, it will be assigned automatically when the cluster is created.

  8. Click Continue.

3. Set up automation⁠

  1. Select the cluster maintenance start time — the time when automatic cluster maintenance actions will start.

  2. Optional: To enable audit logs, check the Audit Logs checkbox . After creating the cluster , configure integration with the log storage and analysis system.

  3. Check the price of a cluster on a dedicated server.

  4. Click Create. Creating a cluster takes up to 60 minutes, during which time the cluster will be in the CREATING status. The cluster will be ready for operation when it enters the ACTIVE status.

    For communication between master and worker nodes on dedicated servers, a private network <cluster_name>-network, private subnet, VLAN and global router <cluster_name>-router will be automatically created, where <cluster_name> is the cluster name. The CIDR subnets of dedicated servers are assigned automatically. If you did not specify the CIDR subnet of the cloud infrastructure when you configured the node groups, it will also be assigned automatically.

    The default security group will be assigned to the node ports. Do not change the rules in it or assign another security group. This will prevent the cluster from failing.