Explore the latest product updates and best practices at our hybrid Checkmk Conference #12 from June 16-18, 2026 – Register here

Werk #19857: kube_pod_status: don't crash when an older status is still cached

Component Checks & agents
Title kube_pod_status: don't crash when an older status is still cached
Date Apr 23, 2026
Level Trivial Change
Class Bug Fix
Compatibility Compatible - no manual interaction needed
Checkmk versions & editions
2.6.0b1
Not yet released
Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT
2.5.0p1 Checkmk Community, Checkmk Pro, Checkmk Ultimate, Checkmk Cloud, Checkmk Ultimate MT

After upgrading a Kubernetes-monitored site, the pod Status service could become UNKNOWN with a traceback ending in KeyError: 'OOMKilled' (or another status name). This happened when the persistent check state still remembered a pod status whose name is no longer in the set the check currently tracks.

The check now tolerates an unknown cached status instead of crashing; the affected pod simply continues with the currently observed status.

To the list of all Werks