Chapter 3. Deploy using local storage devices

Procedure

1. Log in to the OpenShift Web Console.
2. Click Operators → OperatorHub.
3. Type local storage in the Filter by keyword…​ box to search for Local Storage operator from the list of operators and click on it.
4. Click Install.

5. Set the following options on the Install Operator page:

   1. Channel as stable-4.8.
   2. Installation Mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace openshift-local-storage.
   4. Approval Strategy as Automatic.
6. Click Install.

Procedure

1. Log in to OpenShift Web Console.
2. Click Operators → OperatorHub.
3. Search for OpenShift Container Storage from the list of operators and click on it.
4. Click Install.

5. Set the following options on the Install Operator page:

   1. Channel as stable-4.8.
   2. Installation Mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace openshift-storage. If Namespace openshift-storage does not exist, it will be created during the operator installation.
   4. Approval Strategy as Automatic or Manual.

   5. Click Install.

      If you select Automatic updates, the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your operator without any intervention.

      If you select Manual updates, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to have the operator updated to the new version.

Procedure

1. Log into the OpenShift Web Console.

2. Click Operators → Installed Operators to view all the installed operators.

   Ensure that the Project selected is openshift-storage.

3. Click OpenShift Container Storage > Create Instance link of Storage Cluster.

4. Choose Select Mode as Internal-Attached devices.

   Note

   You are prompted to install the Local Storage Operator if it is not already installed. Click Install and follows procedure as described in Installing Local Storage Operator.

5. Discover disks

   1. Choose one of the following:

      • All nodes to discover disks in all the nodes.

      • Select nodes to discover disks from a subset of available nodes.

        Important

        For using arbiter mode, do not select the All nodes option. Instead, use the Select nodes option to select the labeled nodes with attached storage device(s) from the two data-center zones.

   2. Click Next.

6. Create Storage class.

   You can create a dedicated storage class to consume storage by filtering a set of storage volumes.

   1. Enter the Local Volume Set Name.
   2. Enter the Storage Class Name. By default, the volume set name appears for the storage class name. You can also change the name.

   3. The nodes selected for disk discovery in the previous step are displayed in the Filter Disks By section. Choose one of the following:

      • Disks on all nodes to select all the nodes for which you discovered the devices.

      • Disks on select nodes to select a subset of the nodes for which you discovered the devices. Spread the worker nodes across three different physical nodes, racks or failure domains for high availability.

        Important

        The flexible scaling feature gets enabled on creating a storage cluster with 3 or more nodes spread across fewer than the minimum requirement of 3 availability zones. This feature is available only for the new deployments of OpenShift Container Storage 4.7 clusters and does not support the upgraded clusters. For information about flexible scaling, see Scaling Storage Guide.

        Note

        If the nodes to be selected are tainted and not discovered in the wizard, follow the steps provided in the Red Hat Knowledgebase Solution as a workaround to add tolerations for Local Storage Operator resources.

   4. Select SSD/NVME Disk Type from the available list.

   5. Expand the Advanced section and set the following options:

      Volume Mode	Block is selected by default.
      Device Type	Select one or more disk type from the drop down list.
      Disk Size	Set a minimum size of 100GB for the device and maximum available size of the device that needs to be included.
      Maximum Disk Limit	This indicates the maximum number of PVs that can be created on a node. If this field is left empty, then PVs are created for all the available disks on the matching nodes.

   6. Click Next. A pop-up to confirm creation of the new storage class is displayed.
   7. Click Yes to continue.

7. Set Capacity and nodes

   1. Select Storage Class. By default, the new storage class created in the previous step is selected.
   2. Selected Nodes shows the nodes selected in the previous step. This list takes a few minutes to reflect the disks that were discovered in the previous step.
   3. Click Next.

8. (Optional) Set Security and network configuration

   1. Select Enable encryption checkbox to encrypt block and file storage.

   2. Choose one of the following Encryption level:

      • Cluster-wide encryption to encrypt the entire cluster (block and file).
      • Storage class encryption to create encrypted persistent volume (block only) using encryption enabled storage class.

   3. Select Connect to an external key management service checkbox. This is optional for cluster-wide encryption.

      1. Key Management Service Provider is set to Vault by default.
      2. Enter Vault Service Name, host Address of Vault server ('https://<hostname or ip>''), Port number and Token.

      3. Expand Advanced Settings to enter additional settings and certificate details based on your Vault configuration:

         1. Enter the Key Value secret path in Backend Path that is dedicated and unique to OpenShift Container Storage.
         2. (Optional) Enter TLS Server Name and Vault Enterprise Namespace.
         3. Provide CA Certificate, Client Certificate and Client Private Key by uploading the respective PEM encoded certificate file.
         4. Click Save.

9. Select Default (SDN) if you are using a single network or Custom (Multus) Network if you plan on using multiple network interfaces.

   1. Select a Public Network Interface from drop down.

   2. Select a Cluster Network Interface from drop down.

      Note

      If only using one additional network interface select the single NetworkAttachementDefinition (i.e. ocs-public-cluster) for the Public Network Interface and leave the Cluster Network Interface blank.

10. Click Next.
11. Review the configuration details. To modify any configuration settings, click Back to go back to the previous configuration page.
12. Click Create.

13. Edit the configmap if Vault Key/Value (KV) secret engine API, version 2 is used for cluster-wide encryption with Key Management System (KMS).

    1. On the OpenShift Web Console, navigate to Workloads → ConfigMaps.
    2. To view the KMS connection details, click ocs-kms-connection-details.

    3. Edit the configmap.

       1. Click Action menu (⋮) → Edit ConfigMap.

       2. Set the VAULT_BACKEND parameter to v2.

          kind: ConfigMap
          apiVersion: v1
          metadata:
            name: ocs-kms-connection-details
          [...]
          data:
            KMS_PROVIDER: vault
            KMS_SERVICE_NAME: vault
          [...]
            VAULT_BACKEND: v2
          [...]

       3. Click Save.