Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

11.5. Configuring local storage by using the hostpath provisioner

You can configure local storage for virtual machines by using the hostpath provisioner (HPP).

When you install the OpenShift Virtualization Operator, the Hostpath Provisioner Operator is automatically installed. HPP is a local storage provisioner designed for OpenShift Virtualization that is created by the Hostpath Provisioner Operator. To use HPP, you create an HPP custom resource (CR) with a basic storage pool.

11.5.1. Creating a hostpath provisioner with a basic storage pool
リンクのコピー

You configure a hostpath provisioner (HPP) with a basic storage pool by creating an HPP custom resource (CR) with a storagePools stanza. The storage pool specifies the name and path used by the CSI driver.

重要

Do not create storage pools in the same partition as the operating system. Otherwise, the operating system partition might become filled to capacity, which will impact performance or cause the node to become unstable or unusable.

Prerequisites

  • The directories specified in spec.storagePools.path must have read/write access.
  • You have installed the OpenShift CLI (oc).

Procedure

  1. Create an hpp_cr.yaml file with a storagePools stanza as in the following example: 

    apiVersion: hostpathprovisioner.kubevirt.io/v1beta1
kind: HostPathProvisioner
metadata:
  name: hostpath-provisioner
spec:
  imagePullPolicy: IfNotPresent
  storagePools:
  - name: any_name
    path: "/var/myvolumes"
  workload:
    nodeSelector:
      kubernetes.io/os: linux
    • spec.storagePools.name defines the name to identify the source to use. It must be the same as the storagePools name in the StorageClass.yaml.
    • spec.storagePools.path defines the storage pool directories under this node path. Ensure that the path /var/myvolumes value specifies a directory that exists on each worker node.
  2. Save the file and exit.

  3. Create the HPP by running the following command: 

    $ oc create -f hpp_cr.yaml

11.5.1.1. About creating storage classes
リンクのコピー

When you create a storage class, you set parameters that affect the dynamic provisioning of persistent volumes (PVs) that belong to that storage class. You cannot update a StorageClass object’s parameters after you create it.

To use the hostpath provisioner (HPP) you must create an associated storage class for the CSI driver with the storagePools stanza.

注記

Virtual machines use data volumes that are based on local PVs. Local PVs are bound to specific nodes. While the disk image is prepared for consumption by the virtual machine, it is possible that the virtual machine cannot be scheduled to the node where the local storage PV was previously pinned.

To solve this problem, use the Kubernetes pod scheduler to bind the persistent volume claim (PVC) to a PV on the correct node. By using the StorageClass value with volumeBindingMode parameter set to WaitForFirstConsumer, the binding and provisioning of the PV is delayed until a pod is created using the PVC.

11.5.1.2. Creating a storage class for the CSI driver with the storagePools stanza
リンクのコピー

To use the hostpath provisioner (HPP) you must create an associated storage class for the Container Storage Interface (CSI) driver.

When you create a storage class, you set parameters that affect the dynamic provisioning of persistent volumes (PVs) that belong to that storage class. You cannot update a StorageClass object’s parameters after you create it.

Procedure

  1. Create a storageclass_csi.yaml file to define the storage class: 

    apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: hostpath-csi
provisioner: kubevirt.io.hostpath-provisioner
reclaimPolicy: Delete
    1 
    
volumeBindingMode: WaitForFirstConsumer
    2 
    
parameters:
  storagePool: my-storage-pool
    3
    • reclaimPolicy specifies whether the underlying storage is deleted or retained when a user deletes a PVC. The two possible reclaimPolicy values are Delete and Retain. If you do not specify a value, the default value is Delete.

    • volumeBindingMode specifies the timing of PV creation. In this example, the WaitForFirstConsumer configuration delays PV creation until the scheduler assigns a pod to a specific node.

      注記

      Virtual machines use data volumes based on local PVs, which reside on specific nodes. When the system prepares a disk image for the virtual machine, the scheduler might not place the virtual machine on the node where it pinned the local storage PV.

      + To solve this problem, use the Kubernetes pod scheduler to bind the persistent volume claim (PVC) to a PV on the correct node. Setting the volumeBindingMode parameter of the StorageClass to WaitForFirstConsumer delays PV binding and provisioning until you create a pod that uses the PVC.

    • parameters.storagePool specifies the name of the storage pool defined in the HPP custom resource (CR).
  2. Save the file and exit.

  3. Create the StorageClass object by running the following command: 

    $ oc create -f storageclass_csi.yaml
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

Legal Notice

Theme

© 2026 Red Hatトップに戻る