-
Bug
-
Resolution: Done
-
Major
-
None
-
quay-v3.11.0
-
False
-
None
-
False
-
-
-
0
Description:
This is an issue found when deploy Quay 3.11 with Quay 3.11 Operator, when creating QuayRegistry, override the limits/requests to null for quay and mirror components, find after Quay and Mirror POD created, the limits/requests are still existed with default values, pls review this issue.
Quay: quay-operator-bundle-container-v3.11.0-11
QuayRegistry CR:
spec: components: - kind: clair managed: true - kind: postgres managed: true - kind: objectstorage managed: true - kind: redis managed: true - kind: horizontalpodautoscaler managed: true - kind: route managed: true - kind: mirror managed: true overrides: resources: limits: null requests: null - kind: monitoring managed: false - kind: tls managed: true - kind: quay managed: true overrides: resources: limits: null requests: null - kind: clairpostgres managed: true
Quay and mirror pods still has limits/requests even override with null:
