-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
All
-
Production
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
The NUMA Resources Operator should configure out of the box the best setting for the NUMAResourcesScheduler CR informerMode instead of requiring the manual workaround documented in https://docs.google.com/document/d/1jbVeC2dWIp1sK4-O0BxVhtSkagY4cxNrwM8MU3Kksgs/edit?tab=t.0
Version-Release number of selected component (if applicable):
4.19.z
How reproducible:
100%
Steps to Reproduce:
1. install OCP without https://github.com/kubernetes/kubernetes/pull/ 132028 or its backports
Actual results:
the scheduler doesn't work out of the box, requires setting `informerMode` manually
Expected results:
the scheduler should be configured correctly out of the box
Additional info:
- clones
-
OCPBUGS-61409 [4.18] The scheduler informerMode setting should be autoconfigured inspecting the cluster state
-
- Verified
-
- depends on
-
OCPBUGS-61409 [4.18] The scheduler informerMode setting should be autoconfigured inspecting the cluster state
-
- Verified
-
- is cloned by
-
OCPBUGS-61708 [4.16] The scheduler informerMode setting should be autoconfigured inspecting the cluster state
-
- MODIFIED
-
- is depended on by
-
OCPBUGS-61708 [4.16] The scheduler informerMode setting should be autoconfigured inspecting the cluster state
-
- MODIFIED
-
- links to