Grafana Helm Charts Are Moving on 30 Jan 2026

TL;DR: Grafana Labs Helm Charts are moving to a new, community-focused repository. Mark the 30th January 2026. Update your Helm configuration and add the new Helm Chart repository URL https://grafana-community.github.io/helm-charts and replace the old one in your pipelines.

It happened last Tuesday.

Robert’s staging pipeline was completely green. The helm chart was deployed successfully and everything worked perfectly. But two days later, when he tried to push the exact same setup to production, the CI/CD pipeline turned red.

The error message: “Error: looks like https://github.com/corp/helm-charts is not a valid chart repository or cannot be reached: failed to fetch: 404 Not Found“

Robert was confused and lost valuable time debugging to find out the chart repository has been moved. A simple URL change fixed everything, but the time was gone.

Don’t worry, what happened to Robert won’t happen to you!

Here you will find all the information you need about the move of Grafana Labs Helm Charts to a new community-focused repository.

Am I affected?

Are you using Grafana Helm Charts from the official repository with the following URL: https://grafana.github.io/helm-charts? Then MAYBE.

Only a subset of the Helm Charts is being moved. Mimir and Loki are not affected but if you are using grafana-mcp, grafana, synthetic-monitoring-agent, tempo-distributed, tempo-vulture or tempo then ACTION is REQUIRED.

Change the repository URL to the new one https://grafana-community.github.io/helm-charts.

This transition is also being used as a cleanup. Deprecated and End-of-Life (EOL) charts will not be migrated.

The Timeline

The Grafana Labs Helm Charts will be moved to a new community-focused repository on the 30th January 2026.

⚠️ IMPORTANT DATES

Now: Old repository still accessible
January 30, 2026: New repository becomes primary
After Jan 30: No updates on old repository

But don’t panic, your pods won’t stop working after this date.

The old repository remains accessible so existing CI/CD pipelines don’t fail immediately.

But you will stop receiving updates like new versions, bug fixes or security patches if you stay on the old one. So, you need to migrate to the new URL at some point.

How to migrate?

You’ve identified that you are using the affected charts? Now it’s time to grep your codebase. You need to look at your Terraform code, ArgoCD applications, or CI/CD pipelines and switch to the new community repository URL.

Updating the Repository List

For simple command-line usage or scripts, add the new repository.

# add the new repository
helm repo add grafana-community https://grafana-community.github.io/helm-charts

# update repositories
helm repo update

Helm Umbrella Charts

One of the most common setups involves Umbrella Charts that pull sub-charts. In an Umbrella Chart, you define your infrastructure requirements (dependencies) in a Chart.yaml file.

Open your Chart.yaml and locate to the affected dependency and replace the old repository URL to the new one.

Here is an example snippet.

# Chart.yaml

dependencies:
  - name: grafana
    version: 10.5.8
    # ❌ Remove the old reference
    # repository: https://grafana.github.io/helm-charts

    # ✅ Add the new Community reference
    repository: https://grafana-community.github.io/helm-charts

After saving the file, instruct Helm to take a look at the dependency list and to pull in the required dependencies: helm dependency update ./my-chart

It will also generate a lock file that can be used to rebuild the dependencies to an exact version.

Common CI/CD Pitfall

Many CI pipelines cache Helm repositories. Simply changing the URL might not be enough if the runner loads a stale cache.

You can choose between two options to overcome this issue:

manually invalidate the runners cache to ensure the new URL is recognized
explicitly run helm repo update to force an update.

Why is this Migration happening?

You are still here? It seems you are really interested in what is going on at Grafana Labs. Thank you for your patience!
The community around Grafana Helm charts has faced challenges regarding ownership and agility. The previous repository structure required adhering to strict internal corporate security rules mandated by Grafana Labs. This resulted in required internal Grafana reviews, slowing down community contributions.

By forking the repository into a dedicated grafana-community space, the project aims to restore a healthy, fast-moving open-source ecosystem with a clear ownership for community-driven Charts. With trusted community maintainers, PRs, bug fixes, and releases will move faster. This is a positive step towards an active community.

If you are interested in more detailed information take a look at the following discussion.

How can i avoid such problems in the future?

The most reliable way to avoid surprises like a suddenly moved Helm repository is to use something like KumoOps – CloudSecOps as a Service.

With KumoOps, you define which parts of your CloudSecOps we should secure, maintain, and operate for you. So changes like repository migrations, deprecations, and ecosystem shifts don’t turn into latenight debugging sessions or production delays. We keep an eye on the moving parts (tooling, charts, pipelines, security updates), proactively plan required changes, and help ensure your delivery pipelines stay stable over time.