#Configuring Persistent Storage Using Local volumes

#Installing the Local Storage Operator

1. Login, go to the Administrator page.

2. Click Marketplace > OperatorHub to enter the OperatorHub page.

3. Find the Alauda Build of LocalStorage, click Install, and navigate to the Install Alauda Build of LocalStorage page.

   Configuration Parameters:

   Parameter	Recommended Configuration
   Channel	The default channel is stable.
   Installation Mode	Cluster: All namespaces in the cluster share a single Operator instance for creation and management, resulting in lower resource usage.
   Installation Place	Select Recommended, Namespace only support acp-storage.
   Upgrade Strategy	Manual: When there is a new version in the Operator Hub, manual confirmation is required to upgrade the Operator to the latest version.

#Provisioning local volumes by using the Local Storage Operator

Local volumes cannot be created by dynamic provisioning. Instead, persistent volumes can be created by the Local Storage Operator. The local volume provisioner looks for any file system or block volume devices at the paths specified in the defined resource.

1. Create the local volume resource. This resource must define the nodes and paths to the local volumes.

   NOTE

   Do not use different storage class names for the same device. Doing so will create multiple persistent volumes (PVs).

   Execute commands on the control node of the cluster.

   cat << EOF | kubectl create -f -
   apiVersion: "local.storage.openshift.io/v1"
   kind: "LocalVolume"
   metadata:
     name: "local-disks"
     namespace: "acp-storage"
   spec:
     nodeSelector:
       nodeSelectorTerms:
       - matchExpressions:
           - key: kubernetes.io/hostname
             operator: In
             values:
             - worker-01
             - worker-02
             - worker-03
     storageClassDevices:
       - storageClassName: "local-sc"
         forceWipeDevicesAndDestroyAllData: false
         volumeMode: Filesystem
         fsType: xfs
         devicePaths:
           - /path/to/device
   EOF
   1. The namespace where the Local Storage Operator is installed, default is acp-storage.
   2. Optional: A node selector containing a list of nodes where the local storage volumes are attached. This example uses the node hostnames, obtained from kubectl get node. If a value is not defined, then the Local Storage Operator will attempt to find matching disks on all available nodes.
   3. The name of the storage class to use when creating persistent volume objects. The Local Storage Operator automatically creates the storage class if it does not exist. Be sure to use a storage class that uniquely identifies this set of local volumes.
   4. Controls whether the operator wipes the listed devices before use. The default is "false". WARNING: Setting forceWipeDevicesAndDestroyAllData: true is destructive and will erase existing partition tables/filesystem signatures and data on those devices. Use only when you are certain the devices can be safely wiped.
   5. The volume mode, either Filesystem or Block, that defines the type of local volumes.
   6. Optional: The file system that is created when the local volume is mounted for the first time. This parameter must be configured only if volumeMode set to Filesystem.
   7. The path containing a list of local storage devices to choose from.
   8. Replace this value with your actual local disks filepath to the LocalVolume resource by-id, such as /dev/disk/by-id/wwn. PVs are created for these local disks when the provisioner is deployed successfully.

2. Verify that the persistent volumes were created:

   Execute commands on the control node of the cluster.

   kubectl get pv

   Example output:

   NAME                CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
   local-pv-n8xlrd2a   100Gi      RWO            Delete           Available           local-sc                88m
   local-pv-tc78vc73   100Gi      RWO            Delete           Available           local-sc                82m
   local-pv-q86px4df   100Gi      RWO            Delete           Available           local-sc                48m    
   NOTE

   Editing the LocalVolume object does not change the fsType or volumeMode of existing persistent volumes because doing so might result in a destructive operation.

3. Creating the local volume persistent volume claim

   Execute commands on the control node of the cluster.

   cat << EOF | kubectl create -f -
   kind: PersistentVolumeClaim
   apiVersion: v1
   metadata:
     name: local-pvc-name
   spec:
     accessModes:
     - ReadWriteOnce
     volumeMode: Filesystem
     resources:
       requests:
         storage: 100Gi
     storageClassName: local-sc
   EOF  
   1. Name of the PVC.
   2. The type of the PVC. Defaults to Filesystem.
   3. The amount of storage available to the PVC.
   4. Name of the storage class required by the claim.