-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
OpenShift Virtualization 4.20 has a warning:
PodDisruptionBudgetAtLimit Nov 3, 2025, 9:04 AM The pod disruption budget is at the minimum disruptions allowed level. The number of current healthy pods is equal to the desired healthy pods.
$ oc get csv NAME DISPLAY VERSION REPLACES PHASE kubevirt-hyperconverged-operator.v4.20.0 OpenShift Virtualization 4.20.0 kubevirt-hyperconverged-operator.v4.19.6 Succeeded
How reproducible:
Steps to Reproduce:
1. Install OpenShift Virtualization 4.20 on OpenShift 4.20 2. 3.
Expected results: No warning or at least configuration to make it possible to get rid of warnings I can't control.
Additional Info:
It looks like the poddisruptionbudget was added to the SSP operator a few months ago:
https://github.com/kubevirt/ssp-operator/commit/5d59423ed0480758f4c832283f1259b11bf65582
The minimum availability is hard coded.
https://github.com/kubevirt/ssp-operator/commit/5d59423ed0480758f4c832283f1259b11bf65582#diff-a9ef4e14d927674e4e507b28d660a27cfaf7d8610c79c40a5706f9f4db8a78d5R404
So even if I try to add a jsonpatch annotation to reduce the number of replicas it does nothing other than add an additional informational item that I have an unsafe configuration.
ssp.kubevirt.io/jsonpatch: |-
[
{
"op": "replace",
"path": "/spec/templateValidator",
"value": {"replicas": 1}
}
]