Description of problem (please be detailed as possible and provide log
snippests):
Application builds can fail on an error 500 when using the Internal Registry configured with Noobaa as the backend.

Version of all relevant components (if applicable):
4.14.z, 4.15.z

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
When Noobaa is used as a default image registry and configured with default resource settings, it will fail during pushing operations due to the backinstore being OOMKilled.

Is there any workaround available to the best of your knowledge?
Increase the resource requests and limits as per https://access.redhat.com/solutions/7062227

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Unknown

Steps to Reproduce:
    1. Install a cluster
    2. Install/Configure ODF
    3. Configure the internal OCP registry to use a Noobaa bucket as back-end storage via S3
    4. Run an S2I build
    5. The noobaa-default-backing-store-noobaa-pod-XXXXXX pod in the openshift-storage namespace will get OOMKilled during the push to the registry


Actual results:
Builds (and other operations to the internal registry) will fail with and error 500, and the Noobaa BackingStore will go into Phase:Rejected (because the backingstore pod gets OOMKilled)

Expected results:
Builds and other operations to the internal registry should succeed.

Additional info:
The default resource allocation for the backingstore pod appears to be 100m/400Mi. I increased these values to 600m/800Mi and the problem went away.