Documentation Grafana Cloud Monitor infrastructure Kubernetes Monitoring Configure Kubernetes Monitoring

Configure Kubernetes Monitoring

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

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.

Platform choices

You can deploy the Kubernetes Monitoring Helm chart on the following platforms:

• Kubernetes, including:
  • Amazon Elastic Kubernetes Service (EKS) on Amazon Elastic Cloud Compute (EC2)
  • Google Kubernetes Engine (GKE)
• Amazon EKS on AWS Fargate
• Azure Kubernetes Service (AKS)
• Google Kubernetes Engine (GKE) Autopilot
• IBM Cloud Kubernetes Service
• Red Hat OpenShift

Add-ons to configuration

You can also configure with the easy deployment/Helm chart method, and then add on to your configuration for:

• OTel
• Scraping application metrics
• Windows Nodes in AWS EKS Cluster

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 following 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, including:

• Amazon Elastic Kubernetes Service
• Helm and Ansible
• Helm and Argo CD
• Helm and Terraform
• remote-write from Prometheus installations
• Kube-Promtethus Helm stack migration