How to create and modify Managed Service for Kubernetes® clusters

Managed Service for Kubernetes clusters manage and run containerized applications, providing automatic scaling, load balancing and streamlined deployment and management. In this guide, you will learn how to create, modify and delete clusters in Managed Service for Kubernetes. For more information on managing node groups and adding them to clusters, see Creating and modifying Managed Service for Kubernetes® node groups.

How to create clusters

Web console
CLI
Terraform

In the sidebar, go to Compute → Kubernetes.
Click the Create cluster button.
On the page that opens, enter the cluster name.
(Optionally) Enter labels in the key:value format.
Review the Control plane section:
- High availability is enabled by default. As a result, the cluster is created with three etcd stores instead of one. This makes the cluster more reliable; data stored in etcd is accessible even in case of failures. If you want to have only one etcd store, disable the high availability option. However, the enabled option does not affect the cost of the cluster.
- The Kubernetes version is set by default. For supported versions, see Kubernetes® versions in Managed Service for Kubernetes.
- A public endpoint is allocated by default. As a result, the cluster is available from the internet, you can connect to it from any machine. If you want to limit access to the cluster, disable the public endpoint option. Then, you can connect to the cluster only from a virtual machine located in the same subnet with the cluster.
Review the Network section. The network and subnet are selected by default.
Click Create cluster.

Install and configure CLI for Nebius AI Cloud.
Create a cluster:
```
nebius mk8s cluster create \
  --name <cluster_name> \
  --labels <key1=value1,key2=value2,...> \
  --control-plane-endpoints-public-endpoint=<true|false> \
  --control-plane-version 1.33 \
  --control-plane-subnet-id <subnet_ID> \
  --control-plane-etcd-cluster-size <number_of_etcd_stores>
```
The command contains the following parameters:
- --name: The cluster name.
- --labels: Labels in the key=value format.
- --control-plane-endpoints-public-endpoint: Enables a public endpoint. As a result, the cluster is available from the internet, one can connect to it from any machine. If you want to limit access to the cluster, set the parameter to false. Then, one can connect to the cluster only from a virtual machine located in the same subnet with the cluster.
- --control-plane-version: The Kubernetes version. The default and recommended version is 1.32. For supported versions, see Kubernetes® versions in Managed Service for Kubernetes.
- --control-plane-subnet-id: The subnet ID.
- --control-plane-etcd-cluster-size: Number or etcd stores. If you do not specify the number, the cluster is created with three etcd stores. This ensures high availability and makes the cluster more reliable; data stored in etcd is accessible even in case of failures. You can specify a lower number. However, the enabled high availability does not affect the cost of the cluster.

Install and configure the Nebius AI Cloud provider for Terraform.
Create the following configuration file:
```
resource "nebius_mk8s_v1_cluster" "<cluster_name>" {
  name = "<cluster_name>"
  parent_id = "<project_ID>"
  labels = {
    <key1> = "<value1>"
    <key2> = "<value2>"
    ...
    <keyN> = "<valueN>"
  }
  control_plane = {
    endpoints = {
      public_endpoint = {}
    }
    version           = "1.32"
    subnet_id         = "<subnet_ID>"
    etcd_cluster_size = <number_of_etcd_stores>
  }
}
```
The file contains the following parameters:
- name: The cluster name.
- parent_id: The project ID. To copy it, go to the web console and expand the top-left list of projects. Next to the project’s name, click → Copy project ID.
- labels: Labels in the key=value format.
- control_plane: Settings of the cluster’s control plane:
  - endpoints.public_endpoint: Its value {} enables a public endpoint. As a result, the cluster is available from the internet, you can connect to it from any machine. If you want to limit access to the cluster, delete the parameter. Then, one can connect to the cluster only from a virtual machine located in the same subnet with the cluster.
  - version: The Kubernetes version. The default and recommended version is 1.32. For supported versions, see Kubernetes® versions in Managed Service for Kubernetes.
  - subnet-id: The subnet ID.
  - etcd_cluster_size: Number or etcd stores. If you do not specify the number, the cluster is created with three etcd stores. This ensures high availability and makes the cluster more reliable; data stored in etcd is accessible even in case of failures. You can specify a lower number. However, the enabled high availability does not affect the cost of the cluster.
Check that the configuration is correct:
```
terraform validate
```
Apply the changes:
```
terraform apply
```

How to modify clusters

CLI
Terraform

Get the ID of the cluster via its name:

export NB_K8S_CLUSTER_ID=$(nebius mk8s cluster get-by-name \
  --name <cluster_name> --format json | jq -r '.metadata.id')

Alternatively, you can use the listing command: nebius mk8s cluster list.

Update the cluster settings:
```
nebius mk8s cluster update \
  --id $NB_K8S_CLUSTER_ID \
  --labels <key1=value1,key2=value2,...> \
  --control-plane-endpoints-public-endpoint=<true|false> \
  --control-plane-etcd-cluster-size <number_of_etcd_stores>
```
The command contains the following parameters:
- --labels: Labels in the key=value format.
- --control-plane-endpoints-public-endpoint: Enables a public endpoint. As a result, the cluster is available from the internet, one can connect to it from any machine. If you want to limit access to the cluster, set the parameter to false. Then, one can connect to the cluster only from a virtual machine located in the same subnet with the cluster.
- --control-plane-etcd-cluster-size: Number or etcd stores. Three of them ensure high availability of the cluster.
Only the parameters from the command above can be changed. To perform a full cluster update, add --full to the command. This will update all parameters with the default values or the values specified in the --full command.

Modify the manifest with the deployed infrastructure:
```
resource "nebius_mk8s_v1_cluster" "<cluster_name>" {
  name = "<cluster_name>"
  labels = {
    <key1> = "<value1>"
    <key2> = "<value2>"
    ...
    <keyN> = "<valueN>"
  }
  control_plane = {
    endpoints = {
      public_endpoint = {}
    }
    etcd_cluster_size = <number_of_etcd_stores>
  }
}
```
You can change the following parameters:
- name: The cluster name.
- labels: Labels in the key=value format.
- control_plane: Settings of the cluster’s control plane:
  - endpoints.public_endpoint: Its value {} enables a public endpoint. As a result, the cluster is available from the internet, you can connect to it from any machine. If you want to limit access to the cluster, delete the parameter. Then, one can connect to the cluster only from a virtual machine located in the same subnet with the cluster.
  - etcd_cluster_size: Number or etcd stores. If you do not specify the number, the cluster is created with three etcd stores. This ensures high availability and makes the cluster more reliable; data stored in etcd is accessible even in case of failures. You can specify a lower number. However, the enabled high availability does not affect the cost of the cluster.
Check that the configuration is correct:
```
terraform validate
```
Apply the changes:
```
terraform apply
```

How to delete clusters

To delete a cluster, get its ID as shown in How to modify clusters and run the following command:

nebius mk8s cluster delete --id $NB_K8S_CLUSTER_ID

Examples

Creating a cluster with the Kubernetes version 1.32 and a public endpoint for the control plane:

nebius mk8s cluster create \
  --name cluster-example \
  --control-plane-version 1.33 \
  --control-plane-subnet-id \
    $(nebius vpc subnet list --format json \
    | jq -r '.items[0].metadata.id') \
  --control-plane-endpoints-public-endpoint=true

Virtual machines

Slurm and Soperator in Nebius AI Cloud

Managed Service for Kubernetes®

How to create and modify Managed Service for Kubernetes® clusters

How to create clusters

How to modify clusters

How to delete clusters

Examples

Virtual machines

Slurm and Soperator in Nebius AI Cloud

Managed Service for Kubernetes®

​How to create clusters

​How to modify clusters

​How to delete clusters

​Examples

How to create clusters

How to modify clusters

How to delete clusters

Examples