Overview

This check monitors the Kubernetes Controller Manager, part of the Kubernetes control plane.

Note: This check does not collect data for Amazon EKS clusters, as those services are not exposed.

Setup

Installation

The Kubernetes Controller Manager check is included in the Datadog Agent package, so you do not need to install anything else on your server.

Configuration

1. Edit the kube_controller_manager.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your kube_controller_manager performance data. See the sample kube_controller_manager.d/conf.yaml for all available configuration options.

2. Restart the Agent

This integration requires access to the controller manager’s metric endpoint. To have access to the metric endpoint you should:

• have access to the IP/Port of the controller-manager process
• have get RBAC permissions to the /metrics endpoint (the default Datadog Helm chart already adds the right RBAC roles and bindings for this)

Validation

Run the Agent’s status subcommand and look for kube_controller_manager under the Checks section.

Data Collected

Metrics

Events

The Kubernetes Controller Manager check does not include any events.

Service Checks

kube_controller_manager.prometheus.health
Returns CRITICAL if the check cannot access the metrics endpoint.
Statuses: ok, critical

kube_controller_manager.leader_election.status
Returns CRITICAL if no replica is currently set as leader.
Statuses: ok, critical

kube_controller_manager.up
Returns CRITICAL if Kube Controller Manager is not healthy.
Statuses: ok, critical

Troubleshooting

Need help? Contact Datadog Support.