Quay pods (except quay-app) don't get requests set when deployed via Operator

It appears that the only pod created by the Quay Operator (3.5.1) to get Requests (and Limits) set is the "quay-app" pod.

The other pods need at the very minimum requests for CPU and Memory set as well in order to prevent scheduling on Nodes with not enough capacity - especially because there is no way to specify requests via the QuayRegistry CR.

I suspect that this may be a problem with QuayRegistry installations not coming up in a timely manner (it takes 23 minutes on a rather powerful, empty cluster).