Kubelet Server Details Test

The Kubelet is an agent running on each Kubernetes server also called node. It ensures that containers are running in a Pod by managing their life cycle, monitoring their health, and reporting status back to the Kubernetes control plane. It interacts with the container runtime and executes Pod specifications.

Monitoring the Kubelet is crucial for maintaining the health and performance of a Kubernetes cluster. The Kubelet manages the life cycle of containers on each node, ensuring they run as expected and reporting their status to the control plane. By monitoring the Kubelet, you can detect and address issues such as resource exhaustion, container crashes, or network problems promptly. It helps ensure that nodes are healthy, Pods are properly managed, and any discrepancies between desired and actual states are resolved quickly. Effective monitoring of the Kubelet contributes to overall cluster stability and reliability, enhancing the performance of containerized applications.

The Kubelet Server Details Test continuously monitors the kubelet server and reports key metrics like number of running pods, running, created and exited containers 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.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 3:1. This indicates that, by default, detailed measures will be generated every third time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Running pods	Indicates the number of pods running on the target node.	Number	The number of pods running should be enough to support the application demand.
Created containers	Indicates the total number of containers created.	Number	These containers that have been instantiated but are not yet running.
Exited containers	Indicates the number of container exited in last measurement period.	Number	These containers have completed its execution and has stopped running.
Running containers	Indicates the number containers currently running on the target node.	Number