Kubelet Pod Details Test

The Kubelet is an essential component of Kubernetes responsible for managing Pods on a node. It ensures that containers within the Pod are running as expected. Each node in a Kubernetes cluster runs a Kubelet that communicates with the Kubernetes API server to receive Pod specifications and then deploys, monitors, and maintains the containers according to these specs. The Kubelet also handles container health checks and resource management, ensuring that Pods are in the desired state and reporting their status back to the API server. Its primary role is to ensure that the containers are running smoothly and consistently with the specified configurations.

Monitoring Kubelet Pods is essential for maintaining cluster health, ensuring resource efficiency, and quickly identifying issues. It helps track performance, prevent disruptions, and manage resource utilization effectively. Early detection of problems with Kubelet Pods aids in troubleshooting and supports capacity planning, ensuring the overall stability and reliability of the Kubernetes environment.

The Kubelet Pod Details Test continuously monitors the pods in the target node and reports key metrics like duration, number of pods etc. These metrics are invaluable for the administrators to ensure that service is up and prevent any issues in case service has problems.

Target of the test : A Kubernetes Worker Node

Agent deploying the test : A remote agent

Outputs of the test : One set of results for the target Kubernetes Worker node being monitored

Configurable parameters for the test

Parameter	Description
Test Period	How often should the test be executed.
Host	The IP address of the host for which this test is to be configured.
Port	Specify the port at which the specified Host listens. By default, this is 6443.
Timeout	Specify the duration (in seconds) beyond which the test will timeout in the Timeout text box. The default value is 10 seconds.
Metric URL	Each of the Kubernetes system components expose monitoring metrics through /metrics endpoint of the HTTP server. For components that don't expose endpoint by default, refer official Kubernetes distribution documentation site. Specify the metric URL textbox.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Total duration of single pod to go from pending to running	Indicates the time taken for a pod to go from pending to running.	Milliseconds	If this duration is longer or is on increasing trend over a number of observations, it is matter of concern and should be investigated.
Number of single pod to go from pending to running	Indicates the number of pods which are going from pending to running.	Number
Total duration to sync a single pod	Indicates the time taken to sync a single pod.	Milliseconds	If this duration is longer or is on increasing trend over a number of observations, it is matter of concern and should be investigated.
Number of times to sync a single pod	Indicates the number of times it takes to sync a single pod.	Number
Total duration from seeing a pod to starting a worker	Indicates the time it takes from observing a pod to starting the worker on the pod.	Milliseconds	If this duration is longer or is on increasing trend over a number of observations, it is matter of concern and should be investigated.
Number of times from seeing a pod to starting a worker	Indicates the number of times it takes to start the worker on the pod.	Number
Average duration of single pod to go from pending to running	Indicates the average time taken for a pod to go from pending to running.	Milliseconds	The average duration should be within threshold limits.
Average duration to sync a single pod	Indicates the average time taken to sync a single pod.	Milliseconds
Average duration from seeing a pod to starting a worker	Indicates the average time it takes from observing a pod to starting the worker on the pod.	Milliseconds