Impact assessment for OCPBUGS-14605

Which 4.y.z to 4.y'.z' updates increase vulnerability?

• 4.11 -> 4.12.20 and all later until we fix it in 4.12
• 4.12.19 and lower -> 4.12.20 and all later until we fix it in 4.12
• 4.12.z to 4.13.2 and all later until we fix it in 4.13.z
• 4.13.z to 4.13.2 and later builds until we fix it in 4.13.z

Which types of clusters?

• group(csv_succeeded{name=~"kubevirt-hyperconverged-operator[.].*"}) or  0 * group(csv_count)

What is the impact? Is it serious enough to warrant removing update recommendations?

• Containers consuming resources provided by devices plugins are restarted if kubelet is restarted
• For OpenShift Virtualization this means that VMs willl be killed whenever the kubelet is getting restarted (intentionally or unintentionally)

How involved is remediation?

• Upgrade to later 4.12.z or 4.13.z with a fix

Is this a regression?

• Yes, introduced by upstream https://github.com/kubernetes/kubernetes/issues/109595 issue, kubernetes#116376, and its backports in OCPBUGS-14048 (4.13.2) and OCPBUGS-13173 (4.12.20).