Documentation Grafana Cloud Monitor infrastructure Kubernetes Monitoring Configure Kubernetes Monitoring Configure with other methods Helm and Argo CD

Send Kubernetes metrics, logs, and events to Grafana Cloud with Helm and Argo CD

You can use Argo CD to configure Kubernetes Monitoring, and use:

• The Kubernetes Monitoring GUI
• Preconfigured alerts and recording rules

Before you begin

Make sure you have the following available:

• Argo CD installed in your system
• Access to a Kubernetes Cluster
• The Admin role to install preconfigured components

Configuration steps

The steps to configure Kubernetes Monitoring with Terraform are:

1. Use a Grafana Cloud Access Policy token.
2. Install the preconfigured components.
3. Install the Helm chart.

Create or gather Grafana Cloud Access Policy token

You can create a new access policy token or look up an existing token. See Grafana Cloud Access Policies for more information.

You’ll use this token in a future step.

Install preconfigured alerts and recording rules

To install preconfigured alerts and recording rules, complete the following steps:

1. Navigate to your Grafana Cloud account.
2. Click the upper-left menu icon to open the main menu.
3. Click Observability.
4. Click the Kubernetes tile. The Configuration page appears.
5. Under the Backend installation section, click Install to install the alerts and recording rules.

Install the Helm chart using ArgoCD

To install the Kubernetes Monitoring components, complete the following steps.

1. Copy and paste the following configuration into a terminal:

   Copy

   cat >> grafana-k8s-monitoring.yaml <<'EOF'
   apiVersion: argoproj.io/v1alpha1
   kind: Application
   metadata:
       name: grafana-k8s-monitoring
       namespace: {argocd-namespace}
   finalizers:
       - resources-finalizer.argocd.argoproj.io
   spec:
   destination:
       name: ''
       namespace: {namespace}
       server: 'https://kubernetes.default.svc'
   source:
       path: ''
       repoURL: 'https://grafana.github.io/helm-charts'
       targetRevision: ''
       chart: k8s-monitoring
       helm:
           values: |-
               cluster:
                   name: "<cluster-name>"
               externalServices:
                   prometheus:
                       host: "{prometheus-url}"
                       basicAuth:
                           username: "{prometheus-username}"
                           password: "{cloud-access-token}"
                   loki:
                       host: "{loki-url}"
                       basicAuth:
                           username: "{loki-username}"
                           password: "{cloud-access-token}"
               opencost:
                   opencost:
                       exporter:
                           defaultClusterId: "<cluster-name>"
                       prometheus:
                           external:
                               url: "{prometheus-url}/api/prom"
   sources: []
   project: default
   syncPolicy:
       automated:
           prune: true
           selfHeal: true
       retry:
           limit: 2
           backoff:
               duration: 5s
               maxDuration: 3m0s
               factor: 2
       syncOptions:
           - CreateNamespace=true
   EOF

2. Replace the following in the code:

   • {argocd-namespace} with your namespace in which Argo CD is deployed
   • {namespace} with the namespace where you want to deploy Kubernetes Monitoring resources
   • {cluster-name} with the name of your cluster
   • {prometheus-url} with the URL of your Prometheus instance
   • {prometheus-username} with the username of your Prometheus instance
   • {loki-url} with the URL of your Loki instance
   • {loki-username} with the username of your Loki instance
   • {cloud-access-token} with your Grafana Cloud Access token

3. Run the following command:

   shell Copy

   kubectl apply -f grafana-k8s-monitoring.yaml

Next steps

1. Navigate to Kubernetes Monitoring, and click Configuration on the main menu.

2. Click the Metrics status tab to view the data status. Your data begins populating in the view as the system components begin scraping and sending data to Grafana Cloud.