-
Feature Request
-
Resolution: Done
-
Minor
-
None
-
False
-
False
-
Undefined
-
- Proposed title of this feature request
To allow setting cpu restrictions on infra containers
2. What is the nature and description of the request?
Customers may want to restrict the cpus assigned for the containers of
the pod. Every pod has a infra container apart from the containers
that user wants to run. While currently it's possible to restrict the
cpus to the containers but not to the infra containers due to
limitations in the CRI API. We could pursue upstream kubernetes
community to make changes in CRI API to allow setting cpu restrictions
on infra containers too.
However, this is a lower priority task. Infra container typically
aren't running any workload so it's not that they will benefit from
having any restrictions on cpu usage. Also, recently we have added a
capability to drop the infra container altogether
(https://github.com/cri-o/cri-o/pull/4165). So customers who aren't
comfortable with unrestricted infra container can simply drop it from
their infrastructure.
bugzilla ticket https://bugzilla.redhat.com/show_bug.cgi?id=1775444
3. Why does the customer need this? (List the business requirements here)
Better resource management
4. List any affected packages or components.
- is blocked by
-
OCPPLAN-7964 CPU QoS
- Closed