-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.13
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-23328. The following is the description of the original issue:
—
Description of problem:
Unable to change resource limit and request for Secondary Scheduler pods which is created through Secondary Scheduler operator
Version-Release number of selected component (if applicable):
Secondary Scheduler operator 1.1.3 ( observed on current running version and seems it applicable for all the versions)
How reproducible:
Steps to Reproduce:
1. Configure Secondary Scheduler using Secondary Scheduler operator
2. By default the scheduler pods will be assigned below limit and request
~~~
resources:
limits:
cpu: 100m
memory: 500Mi
requests:
cpu: 100m
memory: 500Mi
~~~
3. In larger cluster the limit is not enough, the scheduler pods are frequently getting OOM killed and its affecting pod scheduling
~~~
NAME READY STATUS RESTARTS AGE
secondary-scheduler-75c5b6dc68-d5fq4 1/1 Running 16 (5m31s ago) 66m
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: OOMKilled
Exit Code: 137
~~~
Actual results:
Scheduler pods getting OOM killed and there is no option to increase the resource limit
Expected results:
Scheduler should not get OOM killed and there should an option to increase the resource limit
Additional info:
- clones
-
OCPBUGS-23328 Unable to change resource limit and request for Secondary Scheduler pods which is created through Secondary Scheduler operator
-
- Closed
-
- is blocked by
-
OCPBUGS-23328 Unable to change resource limit and request for Secondary Scheduler pods which is created through Secondary Scheduler operator
-
- Closed
-
- links to
- mentioned on