Chapter 4. Configure storage for OpenShift Container Platform services

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. 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. In the OpenShift Web Console, go to Workloads Config Maps.
2. Set the Project dropdown to openshift-monitoring.
3. Click Create Config Map.

4. Define a new cluster-monitoring-config Config Map using the following example.

   Replace the content in angle brackets (<, >) with your own values, for example, retention: 24h or storage: 40Gi.

   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.

   Example cluster-monitoring-config Config Map

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: cluster-monitoring-config
     namespace: openshift-monitoring
   data:
     config.yaml: |
         prometheusK8s:
           retention: <time to retain monitoring files, e.g. 24h>
           volumeClaimTemplate:
             metadata:
               name: ocs-prometheus-claim
             spec:
               storageClassName: ocs-storagecluster-ceph-rbd
               resources:
                 requests:
                   storage: <size of claim, e.g. 40Gi>
         alertmanagerMain:
           volumeClaimTemplate:
             metadata:
               name: ocs-alertmanager-claim
             spec:
               storageClassName: ocs-storagecluster-ceph-rbd
               resources:
                 requests:
                   storage: <size of claim, e.g. 40Gi>

5. Click Create to save and create the Config Map.

Verification steps

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

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

   3. Verify that 5 Persistent Volume Claims are visible with a state of Bound, attached to three alertmanager-main-* pods, and two prometheus-k8s-* pods.

      Figure 4.1. Monitoring storage created and bound

      

2. Verify that the new alertmanager-main-* pods appear with a state of Running.

   1. Go to Workloads Pods.
   2. Click the new alertmanager-main-* pods to view the pod details.

   3. Scroll down to Volumes and verify that the volume has a Type, ocs-alertmanager-claim that matches one of your new Persistent Volume Claims, for example, ocs-alertmanager-claim-alertmanager-main-0.

      Figure 4.2. Persistent Volume Claims attached to alertmanager-main-* pod

      

3. Verify that the new prometheus-k8s-* pods appear with a state of Running.

   1. Click the new prometheus-k8s-* pods to view the pod details.

   2. Scroll down to Volumes and verify that the volume has a Type, ocs-prometheus-claim that matches one of your new Persistent Volume Claims, for example, ocs-prometheus-claim-prometheus-k8s-0.

      Figure 4.3. Persistent Volume Claims attached to prometheus-k8s-* pod

      

Procedure

1. Deploy storagecluster either from the command line interface or the user interface.

2. Label the application namespace.

   apiVersion: v1
   kind: Namespace
   metadata:
        name: <desired_name>
        labels:
             storagequota: <desired_label>

   <desired_name>

   Specify a name for the application namespace, for example, quota-rbd.

   <desired_label>

   Specify a label for the storage quota, for example, storagequota1.

3. Edit the storagecluster to set the quota limit on the storage class.

   $ oc edit storagecluster -n openshift-storage <ocs_storagecluster_name>

   <ocs_storagecluster_name>

   Specify the name of the storage cluster.

4. Add an entry for Overprovision Control with the desired hard limit into the StorageCluster.Spec:

   apiVersion: ocs.openshift.io/v1
   kind: StorageCluster
   spec:
    [...]
        overprovisionControl:
        - capacity: <desired_quota_limit>
             storageClassName: <storage_class_name>
             quotaName: <desired_quota_name>
             selector:
               labels:
                      matchLabels:
                       storagequota: <desired_label>
   [...]

   <desired_quota_limit>

   Specify a desired quota limit for the storage class, for example, 27Ti.

   <storage_class_name>

   Specify the name of the storage class for which you want to set the quota limit, for example, ocs-storagecluster-ceph-rbd.

   <desired_quota_name>

   Specify a name for the storage quota, for example, quota1.

   <desired_label>

   Specify a label for the storage quota, for example, storagequota1.

5. Save the modified storagecluster.

6. Verify that the clusterresourcequota is defined.

   Note

   Expect the clusterresourcequota with the quotaName that you defined in the previous step, for example, quota1.

   $ oc get clusterresourcequota -A
   
   $ oc describe clusterresourcequota -A