cnv-using-hostpath-provisioner.adoc

Using the hostpath provisioner to enable local storage

To deploy the hostpath provisioner and enable your virtual machines to use local storage, first create a HostPathProvisioner custom resource.

Prerequisites

• Create a backing directory on each node for the PersistentVolumes (PVs) that the hostpath provisioner creates.

• Apply the SELinux context container_file_t to the PV backing directory on each node. For example:

  $ sudo chcon -t container_file_t -R </path/to/backing/directory>

  Note	If you use Red Hat Enterprise Linux CoreOS 8 workers, you must configure SELinux by using a MachineConfig manifest instead.

Procedure

1. Create the HostPathProvisioner custom resource file. For example:

   $ touch hostpathprovisioner_cr.yaml

2. Edit the file, ensuring that the spec.pathConfig.path value is the directory where you want the hostpath provisioner to create PVs. For example:

   apiVersion: hostpathprovisioner.kubevirt.io/v1alpha1
   kind: HostPathProvisioner
   metadata:
     name: hostpath-provisioner
   spec:
     imagePullPolicy: IfNotPresent
     pathConfig:
       path: "</path/to/backing/directory>" (1)
       useNamingPrefix: "false" (2)

   1. Specify the backing directory where you want the provisioner to create PVs.

   2. Change this value to true if you want to use the name of the PersistentVolumeClaim (PVC) that is bound to the created PV as the prefix of the directory name.

      Note	If you did not create the backing directory, the provisioner attempts to create it for you. If you did not apply the container_file_t SELinux context, this can cause Permission denied errors.

3. Create the custom resource in the openshift-cnv namespace:

   $ oc create -f hostpathprovisioner_cr.yaml -n openshift-cnv