Loading...

XML

Word

Printable

Type: Feature
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: openshift-4.14.z, openshift-4.15.z, openshift-4.16.z, openshift-4.17.z
Component/s: Networking
Labels:

Activity Type:
Product / Portfolio Work
Parent Link:
None
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done
Blocked:
False
Blocked Reason:
None
Ready:
False
Size:
None

Target Version:
None
Release Blocker:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Review Complete:
PX Priority Data:
PX Impact Score:
PX Technical Impact:
None
PX Impact Range:
None
PX Scheduling Request:
None
PX Technical Impact Notes:
None

Release Note Text:
Undefined

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".

clones

NE-727 Control the Resource Usage of Ingress Pods

incorporates

RFE-1476 Allow limits and requests in the ingress operator for router pods

Approved

is incorporated by

NE-727 Control the Resource Usage of Ingress Pods

Assignee:: Marc Curry

Reporter:: Marc Curry

Need Info From:: None

Contributors:: None

Architect:: None

QA Contact:: Hongan Li

Doc Contact:: Ashley Hardin

Product Operations Engineering Contact:: None

Votes:: 3 Vote for this issue

Watchers:: 19 Start watching this issue

Created:: 2023/03/09 10:34 AM

Updated:: 2025/10/06 11:48 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates