search
Ctrlk

False Alerts Generated by Alertmanager for KubePersistentVolumeErrors

hashtag
Problem

False alerts regarding "KubePersistentVolumeErrors" are fired by Alertmanager of the Platform9 Prometheus Monitoring Stack deployed using Helm Charts, even though all the Persistent Volumes in the Kubernetes cluster are Bound, Active and Healthy.

name: KubePersistentVolumeErrors
expr: kubepersistentvolume status_phase{job="kube-state-metrics",phase=~"Failed|Pending"} >= 0 for: 5m labels:
severity:critical
annotations: description: The persistent volume {{ $labels.persistentvolume }} has status {{ $labels.phase }}.
runbook_url: https://runbooks.prometheus-operator.dev/runbooks/kubernetes/kubepersistentvolumeerrors summary: PersistentVolume is having issues with provisioning.

hashtag
Environment

  • Platform9 Managed Kubernetes - v5.6.8 and Higher

hashtag
Answer

This is a known issue and is resolved in PMK v5.9.3

hashtag
Additional Information

For more details regarding the bug, please open a support ticket mentioning the JIRA ID: PMK-6219.

PreviousPods Deployed Using Multus Plugin Fail to Have Container Added to Network After Upgrading to WhereabNextWrong Interface/IP Assigned For Kube-apiserver

Last updated