All platform containers should have requests for cpu and memory as described in
The new e2e that verifies this caught this on the ovn jobs (this was the only gap it detected:
fail [github.com/onsi/ginkgo.0-origin.0+incompatible/internal/leafnodes/runner.go:113]: Mar 16 22:22:45.159: Pods in platform namespaces are not following resource request/limit rules or do not have an exception granted:
apps/v1/DaemonSet/openshift-ovn-kubernetes/ovnkube-master/container/sbdb does not have a cpu request (rule: "apps/v1/DaemonSet/openshift-ovn-kubernetes/ovnkube-master/container/sbdb/request[cpu]")
apps/v1/DaemonSet/openshift-ovn-kubernetes/ovnkube-master/container/sbdb does not have a memory request (rule: "apps/v1/DaemonSet/openshift-ovn-kubernetes/ovnkube-master/container/sbdb/request[memory]")
Add both requests and then open a PR to openshift-tests to remove the temporary override (the constraint will report ovnkube-master as a flake on e2e run).
❯ oc get -o yaml -n openshift-ovn-kubernetes ds ovnkube-master
verified on build registry.ci.openshift.org/ocp/release:4.8.0-0.nightly-2021-04-08-005413
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.8.2 bug fix and security 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.