Value Statement

Currently users cannot change the CPU and Memory limits for the MCO operator pod itself. We need a way to configure resource limits for MCO operator, as the MCH is authoritative over the MCO operator yaml. The old way of specifying this in <2.9 no longer works https://access.redhat.com/solutions/7031620 

Definition of Done for Engineering Story Owner (Checklist)

• MCO Operator CPU and Memory requests/limits can be configured without pausing MCH

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.