Chapter 4. Deploy standalone Multicloud Object Gateway

Procedure

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

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

   1. Update Channel as stable.
   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.
5. Click Install.

Procedure

1. Navigate in the left pane of the OpenShift Web Console to click Operators OperatorHub.
2. Scroll or type a keyword into the Filter by keyword box to search for OpenShift Data Foundation Operator.
3. Click Install on the OpenShift Data Foundation operator page.

4. On the Install Operator page, the following required options are selected by default:

   1. Update Channel as stable-4.9.
   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 is created during the operator installation.

5. Select Approval Strategy as Automatic or Manual.

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

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

6. Ensure that the Enable option is selected for the Console plugin.
7. Click Install.

Procedure

1. Log into the OpenShift Web Console.
2. In openshift-local-storage namespace, click Operators Installed Operators to view the installed operators.
3. Click the Local Storage installed operator.
4. On the Operator Details page, click the Local Volume link.
5. Click Create Local Volume.
6. Click on YAML view for configuring Local Volume.

7. Define a LocalVolume custom resource for filesystem PVs using the following YAML.

   apiVersion: local.storage.openshift.io/v1
   kind: LocalVolume
   metadata:
     name: localblock
     namespace: openshift-local-storage
   spec:
     logLevel: Normal
     managementState: Managed
     nodeSelector:
       nodeSelectorTerms:
         - matchExpressions:
             - key: kubernetes.io/hostname
               operator: In
               values:
                 - worker-0
                 - worker-1
                 - worker-2
     storageClassDevices:
       - devicePaths:
           - /dev/sda
         storageClassName: localblock
         volumeMode: Filesystem

   Copy to Clipboard Toggle word wrap

   The above definition selects sda local device from the worker-0, worker-1 and worker-2 nodes. The localblock storage class is created and persistent volumes are provisioned from sda.

   Important

   Specify appropriate values of nodeSelector as per your environment. The device name should be same on all the worker nodes. You can also specify more than one devicePaths.

8. Click Create.

9. Make localblock storage class as the default storage class by annotating it.

   1. Click Storage StorageClasses from the left pane of the OpenShift Web Console.
   2. Click on the localblock storageClass.
   3. Edit the Annotations by adding the Key as storageclass.kubernetes.io/is-default-class and Value as true.
   4. Click Save.

10. In the OpenShift Web Console, click Operators Installed Operators to view all the installed operators.

    Ensure that the Project selected is openshift-storage.

11. Click OpenShift Data Foundation operator and then click Create StorageSystem.
12. In the Backing storage page, expand Advanced.
13. Select Multicloud Object Gateway for Deployment type.
14. Click Next.

15. Optional: In the Security page, select Connect to an external key management service.

    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 the Backend Path that is dedicated and unique to OpenShift Data Foundation.
       2. Optional: Enter TLS Server Name and Vault Enterprise Namespace.
       3. Upload the respective PEM encoded certificate file to provide the CA Certificate, Client Certificate, and Client Private Key.
       4. Click Save.
    4. Click Next.

16. In the Review and create page, review the configuration details:

    To modify any configuration settings, click Back.

17. Click Create StorageSystem.