Managed Kubernetes disks

Managed Kubernetes uses local and network disks of the cloud platform.

You can use local and network volumes in a Managed Kubernetes cluster as boot disk and for data storage.

Using network and local disks in Kubernetes⁠

	Local disks	Network disks
Advantages	Low latency of data access	Ability to store persistent data that needs to be saved when restarting and migrating pods
Limitations	No data availability between pods	There is additional network latency for data access
Objects in Kubernetes	Volumes and VolumeMounts, PersistentVolumes and PersistentVolumeClaims (when installing CSI driver on its own)	PersistentVolumes and PersistentVolumeClaims
Usage	Boot disk Data storage	Boot disk Data storage

Boot (system) disks are used to start and initialize the operating system and applications in Kubernetes containers.

You can use local and network disks of the cloud platform as boot disks.

You select the boot disk when you create the cluster and cannot change it after the cluster is created.

When reinstalling node, all data on boot disks is deleted.

The nodes are being reinstalled:

To store data in Managed Kubernetes clusters, we recommend using PersistentVolumes (PV) on network volumes.

If you installed the CSI driver yourself and created a PV on the local disk, the data will be deleted when you delete the node.