Documentation Grafana Cloud Monitor infrastructure Kubernetes Monitoring Configure Kubernetes Monitoring Configure with Helm chart

Configure Kubernetes Monitoring with easy deployment and Helm chart

The easy deployment process using the Kubernetes Monitoring GUI works in conjunction with the Grafana Kubernetes Monitoring Helm chart. To learn how the Helm chart configuration works, refer to Helm chart overview.

Configuration of the Grafana Kubernetes Monitoring Helm chart includes the steps shown in the following diagram:

Send data from your account

If you need to send data to your account, complete the following steps:

1. Go to your Grafana Cloud account, and click My Account.
2. Select your stack.
3. Click Details next to the name of your stack.
4. At your stack page, click Launch to open Kubernetes Monitoring.
5. Click Start sending data.

Kubernetes Monitoring displays the Cluster configuration tab of the Configuration page.

Configuration process

Complete the configuration process on the Cluster configuration tab.

Prerequisites

Make sure you have met the prerequisites required for these configuration steps. To deploy Kubernetes Monitoring with the Helm chart, you need:

• The Admin role to install alerts
• A Kubernetes Cluster, environment, or fleet you want to monitor
• The kubectl and Helm command-line tools
• Appropriate versions of items related to:
  • kube-state-metrics: Uses client-go to communicate with Clusters. For Kubernetes client-go version compatibility and any other related details, refer to kube-state-metrics.
  • OpenCost: Requires Kubernetes 1.8+ clusters.

Backend Installation

Click Install to install the required, preconfigured alert rules and recording rules.

Select features and enter cluster information

1. In the Cluster name box, enter the name of your Cluster.

2. In the Namespace box, replace default with the namespace where you want to deploy your monitoring infrastructure (the namespace for Grafana Alloy and other dependencies such as kube-state-metrics).

3. Select the platform you are using.

   • Kubernetes, including Amazon Elastic Kubernetes Service (EKS) on Amazon Elastic Cloud Compute (EC2) and Google Kubernetes Engine (GKE)
   • Amazon EKS on AWS Fargate - Node Exporter metrics are disabled. Instead, the Kubernetes API is used to collect Pod logs.
   • Azure Kubernetes Service (AKS)
   • Google Kubernetes Engine (GKE) Autopilot. Node Exporter metrics are not supported on this platform.
   • IBM Cloud Kubernetes Service
   • Red Hat OpenShift

4. Switch on or off the data you want to collect, including:

   • Metrics
   • Cost metrics
   • Energy metrics
   • Cluster events
   • Pod logs
   • OTLP receivers
   • Zipkin receiver

5. Switch on or off whether you want to enable Application Observability for your Cluster.

   Caution

   If you enable Application Observability, this may affect your billing. Refer to Host-based pricing for more details.

6. Switch on or off whether you want your application data to be automatically instrumented using Grafana Beyla.

Use a Grafana.com Access Policy Token

You can create a new access policy token or use an existing token. Refer to Grafana Cloud Access Policies for more information.

To use an existing token:

1. Click Use an existing token.

2. Paste the token into the Access policy token name box.

To create a new token:

1. Click Create a new token.

2. In the box for Access Policy Token name, enter the name of your token.

3. In the expiration date box, select an option for the expiration date.

   The permission scope for the token appears.

4. Click Create token.

   The token generates and appears in the token box. This token is automatically copied into the ConfigMap file.

5. Click the copy icon in the token box to copy the token. Make sure to save it in a secure place. It will not be shown again.

Deploy Monitoring Resources on the Cluster

Deploy the configuration using either the Helm client or Terraform.

Helm client

To use the Helm client to deploy the Kubernetes Monitoring Helm chart to the Cluster:

1. Copy the command.

2. Paste and run it in your terminal.

Terraform

To use Terraform to deploy the Kubernetes Monitoring Helm chart to the Cluster:

1. Copy, modify, and save the following files to your Terraform system set up using Terraform:

   • provider.tf
   • grafana-k8s-monitoring.tf
   • vars.tf

2. Deploy by using the commandsterraform init and terraform apply.

Configure Application Instrumentation

If you chose to include receivers in the Select features and enter cluster information section, a list of endpoints appear. In your application that generates metrics, logs, or traces, enter the appropriate OTLP or Zipkin address.

Done

Click the Metrics status tab to view the status of data collection. Your data becomes populated as the system components begin scraping and sending data to Grafana Cloud. This view shows the health of the different sources of metrics, Pod logs, and Cluster events, as well as any applicable version numbers.

Troubleshoot

Refer to Troubleshooting for any issues that occur after configuration.

Install any integrations

You can use Grafana integrations to monitor the health and status of services and applications running in your Kubernetes clusters.

To install a Kubernetes integration to begin scraping metrics:

1. Click the Integrations tab.

2. Select the integration for the service you want to monitor.

3. Select your preferred deployment method (Helm Chart, Agent, or Agent Operator).

4. Add the provided code snippet to the ConfigMap, or deploy the provided Operator Object. Make sure to replace any template fields with values specific to your service.

5. Click Install integration. Installed integrations display a green checkmark on their tile.

   If you want to use an integration not currently listed on the page, you can use embedded Agent exporters and integrations by configuring them manually. Refer to integrations_config.

6. After installing an integration, redeploy the configuration using the method you originally used.

Retrieve Helm values

If you installed Kubernetes Monitoring with the Helm CLI, you can retrieve the values for your configuration by using the helm get values command.