Description of problem:
Usage of cpu limits is not recommended for cluster managed components as it introduces unnecessary latency, and in general, we can depend on CFS sharing enforced via cpu requests to get proper sharing of cpu time.
An e2e test in origin is attempting to enforce that we maintain this restriction here: https://github.com/openshift/origin/pull/22095
Invalid control plane pods (namespace/pod/container) found with cpu resource limits set
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The machine-config-operator does not belong to the Cloud component.
Verified with 4.0.0-0.nightly-2019-03-07-075403, I've extracted the release-payload and confirmed the CPU limits are removed.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.