Description of problem:

After installing the Operator version 1.4.1 the deployment rhdh-operator becomes briefly healthy before being killed and restarted with an OOM error.

Prerequisites (if any, like setup, operators/versions):

The operator manages a single Backstage Instance.

Steps to Reproduce

1. Install the Operator version with a single Backstage instance present
2. Observe that the rhdh-operator deployment requests 128Mi of memory with a 1Gi limit
3. Observe that the operator becomes healthy for less than 10 seconds before being OOM killed
4. Manually set the memory request to 1Gi and the limit to 2Gi
5. Observe that the pod now becomes healthy and that the memory tops out at 1.22 Gi and stabilizes at 1.07 Gi
6. With the next operator update/reconciliation the memory is reset and the game starts anew

Actual results:

see above

Expected results:

The operator should have a valid memory configuration out of the box for all common use cases.

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Additional info (Such as Logs, Screenshots, etc):