Description of problem:
Getting "The pod distuption budget is preventing further disruption to pods becuase it is at the minimum allowed level" Warning alarm although the PDBs at the namespaces are as per design (min available=1, Allowed Disruptions=0)
Version-Release number of selected component (if applicable):
Silenced the alarms as the current PDBs are expected and there should be some exception alert rule for this.
Shirly please take a look.
This is triggered by PDBs related to VMs, therefore moving to virt.
@acardace @sgott -
I have created this Known Issue release note for 4.10:
* `openshift-monitoring` sends an alert when an application that is protected by a Pod Disruption Budget (PDB) does not allow disruptions for migratable virtual machine images. To workaround this issue, silence the alert by setting OCP Monitoring Results. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2026733[*BZ#2026733*])
However, I am a little unclear on the last point re: OCP monitoring Results. Where can the user see these results? is there a particular field to be set?
Deferring this to 4.12 as the fix requires some time to converge. Multiple teams are involved.
Deferring this to the next release as we still haven't converged on a solution.
Deferring to 4.15, we should re-evaluate this after OCP decision to have KubeVirt silence the alerts.
Closing this one as deferred as we're now tracking it in Jira https://issues.redhat.com/browse/CNV-33834 for 4.16.