Skip to content

volume (PV)

A volume (PersistentVolume, PV) is a piece of storage in the cluster, which can be prepared in advance by the administrator, or dynamically prepared using a storage class (Storage Class). PV is a cluster resource, but it has an independent life cycle and will not be deleted when the Pod process ends. Mounting PVs to workloads can achieve data persistence for workloads. The PV holds the data directory that can be accessed by the containers in the Pod.

Create volume

Currently, there are two ways to create volumes: YAML and form. These two ways have their own advantages and disadvantages, and can meet the needs of different users.

  • There are fewer steps and more efficient creation through YAML, but the threshold requirement is high, and you need to be familiar with the YAML file configuration of the volume.

  • It is more intuitive and easier to create through the form, just fill in the proper values ​​according to the prompts, but the steps are more cumbersome.

YAML creation

  1. Click the name of the target cluster in the cluster list, and then click Container Storage -> Volume (PV) -> Create with YAML in the left navigation bar.

  2. Enter or paste the prepared YAML file in the pop-up box, and click OK at the bottom of the pop-up box.

    Supports importing YAML files from local or downloading and saving filled files to local.

Form Creation

  1. Click the name of the target cluster in the cluster list, and then click Container Storage -> Volume (PV) -> Create Volume (PV) in the left navigation bar.

  2. Fill in the basic information.

    • The volume name, volume type, mount path, volume mode, and node affinity cannot be changed after creation.

    • Volume type: For a detailed introduction to volume types, refer to the official Kubernetes document Volumes.

    • Local: The local storage of the Node node is packaged into a PVC interface, and the container directly uses the PVC without paying attention to the underlying storage type. Local volumes do not support dynamic configuration of volumes, but support configuration of node affinity, which can limit which nodes can access the volume.

    • HostPath: Use files or directories on the file system of Node nodes as volumes, and do not support Pod scheduling based on node affinity.

    • Mount path: mount the volume to a specific directory in the container.

    • access mode:

      • ReadWriteOnce: The volume can be mounted by a node in read-write mode.
      • ReadWriteMany: The volume can be mounted by multiple nodes in read-write mode.
      • ReadOnlyMany: The volume can be mounted read-only by multiple nodes.
      • ReadWriteOncePod: The volume can be mounted read-write by a single Pod.

    • Recycling policy:

      • Retain: The PV is not deleted, but its status is only changed to released , which needs to be manually recycled by the user. For how to manually reclaim, refer to Persistent Volume.
      • Recycle: keep the PV but empty its data, perform a basic wipe ( rm -rf /thevolume/* ).
      • Delete: When deleting a PV and its data.

    • Volume mode:

      • File system: The volume will be mounted to a certain directory by the Pod. If the volume is stored from a device and the device is currently empty, a file system is created on the device before the volume is mounted for the first time.
      • Block: Use the volume as a raw block device. This type of volume is given to the Pod as a block device without any file system on it, allowing the Pod to access the volume faster.

    • Node affinity:

View volume

Click the name of the target cluster in the cluster list, and then click Container Storage -> Volume (PV) in the left navigation bar.

  • On this page, you can view all volumes in the current cluster, as well as information such as the status, capacity, and namespace of each volume.

  • Supports sequential or reverse sorting according to the name, status, namespace, and creation time of volumes.

  • Click the name of a volume to view the basic configuration, StorageClass information, labels, comments, etc. of the volume.

Clone volume

By cloning a volume, a new volume can be recreated based on the configuration of the cloned volume.

  1. Enter the clone page

    • On the volume list page, find the volume to be cloned, and select Clone under the operation bar on the right.

      You can also click the name of the volume, click the operation button in the upper right corner of the details page and select Clone .

  2. Use the original configuration directly, or modify it as needed, and click OK at the bottom of the page.

Update volume

There are two ways to update volumes. Support for updating volumes via forms or YAML files.

Note

Only updating the alias, capacity, access mode, reclamation policy, label, and comment of the volume is supported.

  • On the volume list page, find the volume that needs to be updated, select Update under the operation bar on the right to update through the form, select Edit YAML to update through YAML.

  • Click the name of the volume to enter the details page of the volume, select Update in the upper right corner of the page to update through the form, select Edit YAML to update through YAML.

Delete volume

On the volume list page, find the data to be deleted, and select Delete in the operation column on the right.

You can also click the name of the volume, click the operation button in the upper right corner of the details page and select Delete .