Scheduler Pods Test

The Kubernetes Controller Manager ensures network-related resources are properly managed, including services, network policies, and ingress controllers. It handles tasks like updating services with new endpoints, ensuring pod connectivity, and applying network policies to control traffic. Monitoring the Controller Manager’s network-related activities helps detect issues like misconfigurations, connectivity problems, or resource contention, ensuring consistent networking and communication within the cluster.

Monitoring the Controller Manager's network ensures proper service updates, pod connectivity, and network policy enforcement. It helps detect issues like mis-configurations, network delays, or failures, maintaining seamless communication within the cluster.

This Controller Manager Network Test continuously monitors controller manager network, and reports metrics like requests received, GET requests etc.. These metrics allow the administrator to take informed decision on performance of nodes and take preventive actions if required.

Target of the test : A Kubernetes Master Node

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each node on the target Kubernetes Master node API Server object 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

Request received

Indicates the total number of requests received by Controller manager.

Number

The incoming API requests for managing resources, such as creating, updating, or deleting objects like pods, node

GET requests

Indicates the total number of GET requests received on Controller manager HTTP endpoints.

Number

 

Total request latency

Indicates the sum of all request latency received across all requests.

Milliseconds

Monitoring total request latency helps identify performance bottlenecks, ensure fast response times, and maintain a responsive cluster.

Average request latency

Indicates the average of all request latency received across all requests.

Milliseconds