Skip to main content
Managed Kubernetes disks
Last update:

Managed Kubernetes disks

Managed Kubernetes uses local and networked cloud platform disks.

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

When selecting a disk, consider peculiarities of using local and network disks in Kubernetes.

Using network and local disks in Kubernetes⁠

Local disksNetwork disks
AdvantagesLow latency of data accessAbility to store persistent data that needs to be saved when restarting and migrating pods
LimitationsNo data accessibility between podsThere is additional network latency for data access
Objects in Kubernetes

Volume and VolumeMounts,
PersistentVolumes and PersistentVolumeClaims (when installing the CSI driver yourself)

PersistentVolumes and PersistentVolumeClaims
Utilization
  • Boot disk
  • Data storage
  • Boot disk
  • Data storage

Boot disks⁠

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

You can use the following disks as boot disks local and networked cloud platform 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:

Storage disks⁠

For data storage in Managed Kubernetes clusters we recommend using PersistentVolume (PV) on network disks.

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