-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Control the Resource Usage of Ingress Pods
-
BU Product Work
-
False
-
False
-
To Do
-
OCPSTRAT-363 - Control the Resource Usage of Ingress Pods
-
OCPSTRAT-363Control the Resource Usage of Ingress Pods
-
100% To Do, 0% In Progress, 0% Done
-
Undefined
-
0
-
0
Goal: Allow modifying the resource requests and limits on non-default router deployments.
Problem:
OpenShift Ingress pods are configured with default request values, e.g. 256MiB of memory – an insufficient amount for some customers (one customer example requires ~1GiB), and it is not possible to control the resource usage through the OpenShift Ingress Operator, like the ability to configure/define CPU and Memory "request" and "limit".
Why is this important?
Dependencies (internal and external):
Prioritized epics + deliverables (in scope / not in scope):
Not in scope:
Estimate (XS, S, M, L, XL, XXL):
Previous Work:
Open questions:
Acceptance criteria:
Epic Done Checklist:
- CI - CI Job & Automated tests: <link to CI Job & automated tests>
- Release Enablement: <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- Notes for Done Checklist:
- Adding links to the above checklist with multiple teams contributing; select a meaningful reference for this Epic.
- Checklist added to each Epic in the description, to be filled out as phases are completed - tracking progress towards “Done” for the Epic.
- incorporates
-
RFE-1476 Allow limits and requests in the ingress operator for router pods
- Accepted
-
OCPSTRAT-363 Control the Resource Usage of Ingress Pods
- New
- is cloned by
-
OCPSTRAT-363 Control the Resource Usage of Ingress Pods
- New