This bug was initially created as a copy of Bug #1905298, but for the ingress operator. Containers must set both of these going forward [1], while [2] is showing: openshift-ingress-operator/ingress-operator-5855ff78d5-46l5c container containers[0] (ingress-operator) is not requesting required resources: memory as part of failing: [sig-arch] Managed cluster should ensure control plane containers have requests set for cpu and memory [Suite:openshift/conformance/parallel] origin/25747 is in flight to transition an existing, but overly relaxed, test-case to explicitly require both requests on all containers. Any components which have not been fixed after an initial pass will have temporary exceptions linked to their tracking bugs when the stricter test lands. [1]: https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#resources-and-limits [2]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25747/pull-ci-openshift-origin-master-e2e-gcp/1336048716389289984
verified with 4.7.0-0.nightly-2021-01-10-070949 and passed $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2021-01-10-070949 True False 60m Cluster version is 4.7.0-0.nightly-2021-01-10-070949 $ oc -n openshift-ingress-operator get deployment/ingress-operator -oyaml <---snip---> name: ingress-operator resources: requests: cpu: 10m memory: 56Mi
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633