OCS 4.8 - Cannot increase CPU and/or MEM on noobaa-pod of a new Backing Store based on pvPool

Issue

• We want to use NooBaa’s feature of providing the Backing store for S3 via PVC (local persistent Volume) following these steps:

Create a new Noobaa Backing Store based on pvPool :
4.2.5. Creating a local Persistent Volume-backed backingstore

• For each backingstore volume created, there is a new noobaa-pod created with very low resources (100 mili cores and 400MB), below we have created a new backingstore "new-backings" of type "pv-pool"

[cloud-user@bastion ~]$ noobaa backingstore list
NAME                           TYPE            TARGET-BUCKET                                            PHASE      AGE        
new-backings                   pv-pool                                                                  Creating   24s        


New PVC:
pvc-4d328b15-85f8-4d4e-abb1-497a650518f7   100Gi      RWO            Delete           Bound    openshift-storage/new-backings-noobaa-pvc-5a83e31a       standard                               82m

New nooba pod:
new-backings-noobaa-pod-5a83e31a                                  1/1     Running     0          79m

with only these resources :

    - resources:
        limits:
          cpu: 100m
          memory: 400Mi
        requests:
          cpu: 100m
          memory: 400Mi 

• When we ran few tests we could see that these pods are the bottleneck with respect to CPU and Memory.

• Apparently this capability of increasing cpu and mem is available on the OCS 4.8.8 UI ...but does not work.

From the OCP 4.8 UI :
Installed Operators --> OCS --> Backing Store --> select "your_new_backingstore" --> scroll down and click "edit" pvPool Resource , a window appears to edit CPU, MEM and vol size, you can change values and Save , but nothing changes.