-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.12
on clusters with a large number of services with externalIPs or services from type loadBalancer the ovnkube-node initialization can take up to 50 min
The problem is after a node reboot done by MCO the unschedule taint is removed from the node so the api allocates pods to that node that get stuck on ContrainerCreating and other nodes continue to go down for reboot making the workloads unavailable. (if no PDB exists for the workload to protect it)
- is cloned by
-
OCPBUGS-32426 [4.15z] slow ovnkube-node initialization on large number of services with externalIps
- Closed
- is depended on by
-
OCPBUGS-32426 [4.15z] slow ovnkube-node initialization on large number of services with externalIps
- Closed
- is related to
-
OCPBUGS-33606 Upgrade to latest z-stream before SDN to OVN-Kubernetes migration
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update