Branch: refs/heads/2.1.0
Home:
https://github.com/tribe29/checkmk
Commit: 59c699362f646cc7edb8c9741d34ed43cf8f1824
https://github.com/tribe29/checkmk/commit/59c699362f646cc7edb8c9741d34ed43c…
Author: Solomon Jacobs <solomon.jacobs(a)tribe29.com>
Date: 2022-03-07 (Mon, 07 Mar 2022)
Changed paths:
A .werks/13344
M checkman/kube_pod_status
M cmk/base/plugins/agent_based/kube_pod_status.py
M cmk/gui/plugins/wato/check_parameters/kube.py
M cmk/gui/plugins/wato/check_parameters/kube_pod_status.py
M tests/unit/cmk/base/plugins/agent_based/test_kube_pod_status.py
Log Message:
-----------
13344 KUBE: kube_pod_status updated rule set
The status of a pod with an erronous container will often change. This happens even if
there is
no meaningful change in the underlying problem. Previously, the kube_pod_status check
would alert
if a specific status would persist for too long. However, changes of status would reset
the
corresponding timer. The new rule set allows configuring a timer for a group of statuses.
CMK-9837
Change-Id: Ic2a9a1b9e3861fa58b31b4fe4bc0c0d94ebd1e12