---
title: "Create a Managed Kubernetes cluster on a dedicated server"
sidebar_label: "Create a cluster on a dedicated server"
sidebar_position: 3
description: "How to create a Managed Kubernetes cluster on a dedicated server"
---

import Formbricks from '@theme/MDXComponents/Formbricks'
import Tabs from '@theme/Tabs'
import TabItem from '@theme/TabItem'

# Create a Managed Kubernetes cluster on a dedicated server

You can create a Managed Kubernetes cluster with a node group on a [dedicated server](/dedicated/about/about-dedicated.mdx).

Dedicated servers are used when you need:

* consistently high performance;
* an increased level of privacy;
* reserved resources.

In Managed Kubernetes, you can use [prebuilt configuration dedicated servers](/managed-kubernetes/node-groups/configurations.mdx#configurations-for-dedicated-nodes) with a local port.

A dedicated server is already assembled, mounted, and joined to a private L3 network with the Kubernetes Control Plane using a [Global Router](/global-router/).

You can create no more than 10 high-availability clusters and 10 basic Managed Kubernetes clusters on dedicated servers within a single project and a single pool.

When selecting clusters on dedicated servers, consider the [limitations](/managed-kubernetes/about/about-managed-kubernetes.mdx#limitations-of-dedicated-cluster).

1. [Configure the cluster](#configure-cluster).
2. [Configure the node group](#configure-node-group).
3. [Configure automation](#configure-automation).

### 1. Configure the cluster \{#configure-cluster}

1. In the [control panel](https://my.selectel.ru/mks/), in the top menu, click **Products** and select **Managed Kubernetes**.

2. In the **Clusters** section, click **Create cluster**.

3. Enter the cluster name. The name will be displayed in cluster object names: node groups, nodes, load balancers, networks, and volumes. For example, if the cluster name is `kelsie`, the node group name will be `kelsie-node-gdc8q`, and the boot volume name will be `kelsie-node-gdc8q-volume`.

4. Select a [location](/infrastructure/locations.mdx) for the master nodes. Once the cluster is created, you cannot change the location.

5. Select a [Kubernetes version](/managed-kubernetes/about/about-managed-kubernetes.mdx#versions).

6. Optional: select a network plugin (CNI). Calico is used in the cluster by default. You cannot change the CNI after the cluster is created.

   In the Cilium network plugin, by default:

   * the `envoy daemonset` setting is enabled – for more information, see the [Envoy](https://docs.cilium.io/en/latest/security/network/proxy/envoy/#envoy) article in the Cilium documentation;
   * the `hubble-relay` setting is disabled – for more information, see the [Hubble Relay](https://docs.cilium.io/en/stable/internals/hubble/#hubble-relay) subsection of the Hubble internals article in the Cilium documentation.

   If you want to change these settings, create a cluster using the [Managed Kubernetes API](https://docs.selectel.ru/api/managed-kubernetes/). Note that using the `hubble-relay` setting requires at least 4 GB of RAM on the node.

7. Select a [cluster type](/managed-kubernetes/about/about-managed-kubernetes.mdx#cluster-types). Once the cluster is created, you cannot change the cluster type.

8. Optional: to make the cluster accessible via a private network and inaccessible from the internet, select the **Private kube API** checkbox. By default, the cluster is created in a public network and is automatically assigned a public kube API IP address accessible from the internet. Once the cluster is created, you cannot change the kube API access type.

9. Click **Continue**.

### 2. Configure the node group \{#configure-node-group}

You can add only one node group when creating a cluster. You can [add additional node groups](/managed-kubernetes/node-groups/create-node-group.mdx#add-node-group-with-dedicated-nodes) to an existing cluster.

1. In the **Server type** field, select **Dedicated server**.

2. Select a [location](/infrastructure/locations.mdx#pool) for all worker nodes in the group. Once the cluster is created, you cannot change the location.

3. Configure the worker node settings in the group:

   3.1. Нажмите **Выбрать конфигурацию**.

   3.2. Выберите [тарифный план](/managed-kubernetes/about/payment.mdx#billing-option-types).

   3.3. Select a prebuilt configuration for dedicated servers. Disks in all configurations are combined into RAID1 — all data is simultaneously written to two physical disks in the RAID array.

   3.4. Нажмите **Выбрать**.

   You cannot change the node configuration after the cluster is created.

4. Optional: change the default [disk partitioning](/managed-kubernetes/node-groups/disc-partitioning-in-dedicated-cluster.mdx):

   4.1. В поле **Разметка диска** нажмите **Изменить**.

   4.2. Чтобы отказаться от раздела `/storage`, снимите чекбокс **/storage**.

   4.3. Чтобы изменить размер корневого раздела `/`, in строке корневого раздела измените количество гигабайт, выделяемых для этого раздела. Минимальный размер — 30 ГБ. Максимальный размер — меньше размера диска on 2 ГБ (1 ГБ для раздела `/boot` and 1 ГБ для раздела `/storage`).

   4.4. Нажмите **Сохранить**.

5. Configure the quantity of worker nodes:

   5.1. Откройте вкладку **Фиксированное**.

   5.2. Specify the number of nodes. For high-availability of system components and the Cilium network plugin, we recommend having at least two worker nodes in the cluster; nodes can be in different groups.

6. Optional: in поле **CIDR подсети группы нод** введите CIDR новой приватной подсети, которая будет использоваться для рабочих нод группы.

   The subnet must meet the following conditions:

   * принадлежит к диапазону приватных адресов `10.0.0.0/8`, `172.16.0.0/12` or `192.168.0.0/16`;
   * has a size of `/24`;
   * не пересекается with диапазонами `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`. Эти диапазоны участвуют во внутренней адресации Managed Kubernetes.

   The subnet will be created in a separate VLAN. If you do not specify a CIDR, one will be assigned automatically when the cluster is created.

7. Optional: add node group labels:

   7.1. В поле **Метки** нажмите **Добавить**.

   7.2. Enter the label key.

   7.3. Enter the label value.

   7.4. Нажмите **Добавить**.

8. Optional: add node group taints:

   8.1. В поле **Тейнты** нажмите **Добавить**.

   8.2. Enter the taint key.

   8.3. Введите значение тейнта.

   8.4. Select an effect:

   * NoSchedule — new pods will not be added, and existing ones will continue to run;
   * PreferNoSchedule — new pods will be added if no other free space is available in the cluster;
   * NoExecute — running pods without tolerations will be evicted.

   8.5. Нажмите **Добавить**.

9. Optional: add a script with custom parameters to configure the Managed Kubernetes cluster:

   9.1. В поле **User data** нажмите **Добавить**.

   9.2. Вставьте скрипт. Максимальный размер скрипта with данными, которые не закодированы in Base64, — 47 КБ. Примеры скриптов and поддерживаемые форматы можно посмотреть in инструкции [User data](/managed-kubernetes/node-groups/user-data.mdx).

10. Optional: in the **Cloud network** block, in the **Cloud infrastructure subnet** field, enter the CIDR of the new private subnet to be used for communication between master nodes and the service global router.

    The subnet must meet the following conditions:

    * принадлежит сети проекта, in котором вы создаете кластер. К какому проекту относится сеть можно посмотреть in [панели управления](https://my.selectel.ru/vpc/default/networks/): in верхнем меню нажмите **Продукты** → **Managed Kubernetes** → **Сеть** → вкладка **Приватные сети** → карточка сети. Если сеть принадлежит другому проекту, in карточке сети будет тег **Кросспроектная** and информация об идентификаторе проекта, in котором она была создана;
    * подсеть должна быть приватной — принадлежать к диапазону `10.0.0.0/8`, `172.16.0.0/12` or `192.168.0.0/16`;
    * the subnet size must be `/24`;
    * подсеть не должна пересекаться with диапазонами `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`. Эти диапазоны участвуют во внутренней адресации Managed Kubernetes;
    * the subnet must not overlap with the CIDR of the node group subnet you assigned in step 8.

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

11. Click **Continue**.

### 3. Set up automation \{#configure-automation}

1. Select the [cluster maintenance start time](/managed-kubernetes/clusters/set-up-maintenance-window.mdx) — the time when automatic cluster maintenance actions will begin.

2. Optional: to enable [audit logs](/managed-kubernetes/clusters/logs.mdx), select the **Audit logs** checkbox. After the cluster is created, [configure integration with a log storage and analysis system](/managed-kubernetes/clusters/logs#configure-export-of-audit-logs).

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

4. Нажмите **Создать**. Создание кластера занимает до 60 минут, in это время кластер будет находиться in [статусе](/managed-kubernetes/clusters/cluster-statuses.mdx) `CREATING`. Кластер будет готов к работе, когда перейдет in статус `ACTIVE`.

   To connect master nodes and worker nodes on dedicated servers, a private network `<cluster_name>-network`, a private subnet, a VLAN, and a global router `<cluster_name>-router` will be created automatically, where `<cluster_name>` is the cluster name. The CIDR of the dedicated server subnet is assigned automatically. If you did not specify a cloud infrastructure subnet CIDR when [configuring node groups](#configure-node-group), it will also be assigned automatically.

   The [default security group](/cloud-servers/security-groups/about-security-groups.mdx#default-security-group) will be assigned to the node ports. Do not change the rules within it and do not assign a different security group. Doing so may cause cluster malfunction.

<Formbricks />