Description of problem:

When upgrading from CNV 4.8.0 to 4.8.2 if there are running VMIs with 'EvictionStrategy: LiveMigrate' the associated disruption budgets will keep existing forever since the VMI-PDB logic changed in 4.8.1 and those old PDBs do not get properly reconciled, this might continuously trigger alerts about not having enough pods compared to the pods the PDB expects to protect (as until 4.8.1 the logic was to create a single PDB with 'MinAvailable: 2' at all times).

The quick workaround is to delete all pdbs associated to running VMIs so that virt-controller will notice the deletions and re-create the PDBs with the correct values, to do that simply run:

(assuming the VMIs are in the default namespace)
kubectl delete pdb --all

otherwise

kubectl -n $NAMESPACE delete pdb --all

Version-Release number of selected component (if applicable):

How reproducible:
Always

Steps to Reproduce:
1. Install CNV 4.8.0
2. Create a VMI with 'EvictionStrategy: LiveMigrate'
3. Upgrade to CNV 4.8.2

Actual results:
The VMI associated PDB has 'MinAvailable: 2'.

Expected results:
The VMI associated PDB should have 'MinAvailable: 1'.

Additional info: