Custom configuration for Kubernetes Monitoring via AWS EKS Cluster Add-on

Hello everybody, I am a new Grafana Cloud User, I am happy to be here and hopeful to find help in this community.

What are you trying to achieve?

I want to use the Grafana Cloud Kubernetes Monitoring integration within my AWS EKS clusters and I would like to use the official AWS EKS Cluster Add-on for the installation.

What Grafana version and what operating system are you using?

I am using the latest version of the AWS EKS Cluster Add-on: v0.13.1-eksbuild.1
As well as the following versions of:

  • aws cli: aws-cli/2.15.50 Python/3.11.9 Darwin/23.4.0
  • eksctl: 0.176.0-dev

How are you trying to achieve it?

I followed the official documentation on grafana.com:
Configure Kubernetes Monitoring as an Add-on with an AWS EKS Cluster

Moreover, I would like to provide a specific configuration for the installation of the EKS add-on.
Therefore, I followed the instructions as well:

  1. Download the json schema of the add-on in order to validate your configuration

  2. Write a configuration file:

    {
        "cluster": {
            "name": "production"
        },
        "metrics": {
            "enabled": true,
            "cost": {
                "enabled": true
            },
            "node-exporter": {
                "enabled": true
            }
        },
        "logs": {
            "enabled": true,
            "pod_logs": {
                "enabled": true
            },
            "cluster_events": {
                "enabled": true
            }
        },
        "traces": {
            "enabled": true
        },
        "receivers": {
            "grpc": {
                "enabled": false
            },
            "http": {
                "enabled": false
            },
            "zipkin": {
                "enabled": false
            }
        },
        "opencost": {
            "enabled": true
        },
        "kube-state-metrics": {
            "enabled": true
        },
        "prometheus-node-exporter": {
            "enabled": true
        },
        "prometheus-operator-crds": {
            "enabled": true
        }
    }
    

    The content of this file is similar to the configuration created in the Grafana Console if one provisions the kubernetes-monitoring integration.
    Moreover, is should be valid against the schema.

What happened?

When I tried to deploy this configuration with eksctl, the cli tool told me over and over again that basically all json properties were unknown.
Hence, the most recent version of eksctl wasn’t able to install anything.

When I tried the official aws cli, the validation of the json configuration file worked, however, I got an error in the AWS EKS console:

What did you expect to happen?

That all Grafana components would be installed according to the configuration provided.

I would be really grateful for help at this point.
Because if we can’t figure our a reliable way to configure the Grafana integration and installation via EKS add-on, this whole approach would become useless.