Chapter 4. Configure storage for OpenShift Container Platform services

Procedure

1. Create ObjectBucketClaim by following the steps in Creating Object Bucket Claim.

2. Create an image-registry-private-configuration-user secret.

   1. Go to the OpenShift web-console.
   2. Click ObjectBucketClaim -→ ObjectBucketClaim Data.
   3. In the ObjectBucketClaim data, look for MCG access key and MCG secret key in the openshift-image-registry namespace.

   4. Create the secret using the following command:

      $ oc create secret generic image-registry-private-configuration-user --from-literal=REGISTRY_STORAGE_S3_ACCESSKEY=<MCG Accesskey> --from-literal=REGISTRY_STORAGE_S3_SECRETKEY=<MCG Secretkey> --namespace openshift-image-registry

3. Change the status of managementState of Image Registry Operator to Managed.

   $ oc patch configs.imageregistry.operator.openshift.io/cluster --type merge -p '{"spec": {"managementState": "Managed"}}'

4. Edit the spec.storage section of Image Registry Operator configuration file:

   1. Get the unique-bucket-name and regionEndpoint under the Object Bucket Claim Data section from the Web Console OR you can also get the information on regionEndpoint and unique-bucket-name from the command:

       $ oc describe  noobaa

   2. Add regionEndpoint as http://<Endpoint-name>:<port> if the

      • storageclass is ceph-rgw storageclass and the
      • endpoint points to the internal SVC from the openshift-storage namespace.

   3. An image-registry pod spawns after you make the changes to the Operator registry configuration file.

      $ oc edit configs.imageregistry.operator.openshift.io -n openshift-image-registry
      apiVersion: imageregistry.operator.openshift.io/v1
      kind: Config
      metadata:
      [..]
      name: cluster
      spec:
      [..]
      storage:
      s3:
      
        bucket: <Unique-bucket-name>
      
        region: us-east-1 (Use this region as default)
      
        regionEndpoint: https://<Endpoint-name>:<port>
      
        virtualHostedStyle: false

5. Reset the image registry settings to default.

   $ oc get pods -n openshift-image-registry

Procedure

1. Create a Persistent Volume Claim for the Image Registry to use.

   1. In the OpenShift Web Console, click Storage → Persistent Volume Claims.
   2. Set the Project to openshift-image-registry.

   3. Click Create Persistent Volume Claim.

      1. From the list of available storage classes retrieved above, specify the Storage Class with the provisioner openshift-storage.cephfs.csi.ceph.com.
      2. Specify the Persistent Volume Claim Name, for example, ocs4registry.
      3. Specify an Access Mode of Shared Access (RWX).
      4. Specify a Size of at least 100 GB.

      5. Click Create.

         Wait until the status of the new Persistent Volume Claim is listed as Bound.

2. Configure the cluster’s Image Registry to use the new Persistent Volume Claim.

   1. Click Administration → Custom Resource Definitions.
   2. Click the Config custom resource definition associated with the imageregistry.operator.openshift.io group.
   3. Click the Instances tab.
   4. Beside the cluster instance, click the Action Menu (⋮) → Edit Config.

   5. Add the new Persistent Volume Claim as persistent storage for the Image Registry.

      1. Add the following under spec:, replacing the existing storage: section if necessary.

           storage:
             pvc:
               claim: <new-pvc-name>

         For example:

           storage:
             pvc:
               claim: ocs4registry

      2. Click Save.

3. Verify that the new configuration is being used.

   1. Click Workloads → Pods.
   2. Set the Project to openshift-image-registry.
   3. Verify that the new image-registry-* pod appears with a status of Running, and that the previous image-registry-* pod terminates.
   4. Click the new image-registry-* pod to view pod details.
   5. Scroll down to Volumes and verify that the registry-storage volume has a Type that matches your new Persistent Volume Claim, for example, ocs4registry.

Procedure

1. Click Administration → Custom Resource Definitions from the left pane of the OpenShift Web Console.
2. On the Custom Resource Definitions page, click ClusterLogging.
3. On the Custom Resource Definition Overview page, select View Instances from the Actions menu or click the Instances Tab.

4. On the Cluster Logging page, click Create Cluster Logging.

   You might have to refresh the page to load the data.

5. In the YAML, replace the storageClassName with the storageclass that uses the provisioner openshift-storage.rbd.csi.ceph.com. In the example given below the name of the storageclass is ocs-storagecluster-ceph-rbd:

   apiVersion: "logging.openshift.io/v1"
   kind: "ClusterLogging"
   metadata:
     name: "instance"
     namespace: "openshift-logging"
   spec:
     managementState: "Managed"
     logStore:
       type: "elasticsearch"
       elasticsearch:
         nodeCount: 3
         storage:
           storageClassName: ocs-storagecluster-ceph-rbd
           size: 200G # Change as per your requirement
         redundancyPolicy: "SingleRedundancy"
     visualization:
       type: "kibana"
       kibana:
         replicas: 1
     curation:
       type: "curator"
       curator:
         schedule: "30 3 * * *"
     collection:
       logs:
         type: "fluentd"
         fluentd: {}

   If you have tainted the OpenShift Data Foundation nodes, you must add toleration to enable scheduling of the daemonset pods for logging.

   spec:
   [...]
     collection:
       logs:
         fluentd:
           tolerations:
           - effect: NoSchedule
             key: node.ocs.openshift.io/storage
             value: 'true'
         type: fluentd

6. Click Save.

Verification steps

1. Verify that the Persistent Volume Claims are bound to the elasticsearch pods.

   1. Go to Storage → Persistent Volume Claims.
   2. Set the Project dropdown to openshift-logging.

   3. Verify that Persistent Volume Claims are visible with a state of Bound, attached to elasticsearch-* pods.

      Figure 4.4. Cluster logging created and bound

      

2. Verify that the new cluster logging is being used.

   1. Click Workload → Pods.
   2. Set the Project to openshift-logging.
   3. Verify that the new elasticsearch-* pods appear with a state of Running.
   4. Click the new elasticsearch-* pod to view pod details.
   5. Scroll down to Volumes and verify that the elasticsearch volume has a Type that matches your new Persistent Volume Claim, for example, elasticsearch-elasticsearch-cdm-9r624biv-3.
   6. Click the Persistent Volume Claim name and verify the storage class name in the PersistentVolumeClaim Overview page.