Configure Kubernetes Monitoring

You have many options for configuration, depending on your circumstances and the technologies you prefer.

Note
Kubernetes Monitoring is available only in Grafana Cloud, and only supports data sources hosted in Grafana Cloud.

Configure with Grafana Kubernetes Monitoring Helm chart

To send infrastructure data to Grafana Cloud, it is easiest to configure with the Grafana Kubernetes Monitoring Helm chart, which deploys Grafana Alloy. With this method, you can send metrics, logs, events, traces, and cost metrics.

Note
Configuration with Grafana Kubernetes Monitoring Helm chart is recommended.

Upgrade from Grafana Agent or Agent Operator

If you have already configured with either Agent static mode or Agent Operator, you can upgrade and migrate to Grafana Kubernetes Monitoring Helm chart with the appropriate method:

Upgrade from Agent static mode to Grafana Kubernetes Monitoring Helm chart.
Upgrade from Agent Operator to Grafana Kubernetes Monitoring Helm chart.

Configure by other methods

There are other methods you can use to configure Kubernetes Monitoring.

Send previously collected data to Grafana Cloud

If you are already collecting telemetry data for your infrastructure and want to send it to Grafana Cloud, refer to the options available in Configure manually for infrastructure.

Note
You should have only one job scraping kube-state-metrics. If you have multiple scrape jobs running at the same time, you might see an error similar to this error when you try to view objects in Cluster navigation: execution: found duplicate series for the match group...

Configure for an Amazon EKS Cluster

If you want to monitor Windows Nodes within an Amazon Elastic Kubernetes Service (EKS) cluster, refer to Configure Windows Exporter to monitor Windows Nodes.

To configure Kubernetes Monitoring on your EKS Cluster, refer to Configure Kubernetes Monitoring on an AWS EKS Cluster.