Skip to content

Commit 84963a4

Browse files
committed
kube_replicas: Update checkman, terminating pods
This was missed in the recent update to allow `kube_replicas` to monitor terminating pods in a Deployment's ReplicaSet. Change-Id: I3909f1773f220f9d992e97d7d473f292d626aaaf
1 parent e495384 commit 84963a4

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

packages/cmk-plugins/cmk/plugins/kube/checkman/kube_replicas

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,14 @@ description:
77
This check monitors the number of Kubernetes replicas.
88

99
In the event that the number of ready or up-to-date replicas is below the
10-
number of desired replicas, the check shows a WARN and CRIT state if this
11-
persists for more than 5 minutes and 10 minutes respectively. Moreover,
12-
if there are misscheduled Pods controlled by a DaemonSet, then the check
13-
will also show WARN/CRIT, after 5/10 minutes.
10+
number of desired replicas, the check by default shows a WARN and CRIT state
11+
if this persists for more than 5 minutes and 10 minutes respectively.
12+
13+
Additionally, the following are monitored and subject to the same defaults
14+
described above:
15+
16+
- Misscheduled Pods controlled by a DaemonSet
17+
- Terminating Pods controlled by a Deployment
1418

1519
The check also monitors the number of replicas that are available. However, this
1620
is only done if the MinReadySeconds field is non-zero. For MinReadySeconds = 0,

0 commit comments

Comments
 (0)