Check-Manual von kube_pod_resources_with_capacity
| Kubernetes: Pod Resources | |
|---|---|
| Distribution | offizieller Teil von Check_MK |
| Lizenz | GPL |
| Unterstützte Agenten | Kubernetes |
- running
- pending
- failed
- succeeded
- unknown
Moreover, the check monitors the number of allocatable pods, the pod capacity and the number of free pods available on the node/cluster. The number of free pods is equal to the number of allocatable pods minus the number of pending and running pods.
Upper levels for WARN/CRIT can be defined for the time a pod is pending.
The duration a pod is pending is calculated based on the time checkmk has seen the pod, not on data
provided by the Kubernetes API. This means the pending phase duration is zero when the
monitoring first begins, even if there are pods, which have been pending for much longer. By
default, any time a pod spends pending is tolerated and the service remains OK.
If a pod exceeds the tolerating time period, the pod name will be displayed next to the number of pods. If there are more than three pods exceeding the time limit, only the those three pods, which have been in the pending phase the longest will be shown.
For pods in the phase unknown, the state of the check result is configurable. By default the service goes UNKNOWN, if there are unknown pods. The pod names are displayed in similar fashion as for the pending pods. However, pod names are not displayed based on how long they have been unknown.
The check requires that the special agent kube is configured.
