chore(base-cluster/monitoring): migrate helm repo to new URL

[cwrau]

See grafana-community/helm-charts#2

Summary by CodeRabbit

Release Notes

• Chores
  • Updated Helm chart repository configuration for monitoring and tracing services
  • Adjusted installation dependencies to require tracing enablement alongside monitoring components

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[gemini-code-assist]

Summary of Changes

Hello @cwrau, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request facilitates the migration of the Grafana Tempo Helm chart to its new community-maintained repository. It updates the chart's source reference and introduces the new repository definition within the configuration, ensuring that the base-cluster setup correctly fetches and deploys the Tempo chart from its updated location. This change aligns the project with the new distribution channel for Grafana community Helm charts.

Highlights

• Helm Repository Migration: The Helm chart specification for grafana-tempo has been updated to reference the grafana-community repository instead of the older grafana repository.
• New Helm Repository Definition: A new grafana-community entry has been added to values.yaml, defining its URL as https://grafana-community.github.io/helm-charts.
• Tempo Chart Relocation: The tempo chart's version and its enabling condition have been moved from under the general grafana repository definition to the newly defined grafana-community repository in values.yaml.
• Condition Simplification: The general condition for the grafana repository in values.yaml has been simplified to only depend on monitoring.prometheus.enabled.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Warning

Rate limit exceeded

@cwrau has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 24 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

This PR switches the Grafana Tempo chart source repository from grafana to grafana-community in the HelmRelease configuration and adds the corresponding Helm repository entry. The condition for the grafana repository is updated to require both Prometheus and Tracing to be enabled.

Changes

Cohort / File(s)	Summary
Tempo Chart Source charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml	Changes the Tempo chart source repository from grafana to grafana-community in the HelmRelease chartSpec.
Helm Repository Configuration charts/base-cluster/values.yaml	Adds new Helm repo grafana-community with the tempo chart and updates the grafana repository condition to require both Prometheus and Tracing enabled (previously Prometheus and either Loki or Tracing).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• #1862: Modifies the base-cluster Grafana Tempo chart source and related tracing/tempo configuration.
• #1875: Modifies Grafana Tempo chart references and Helm repository/chart configuration.
• #1758: Modifies HelmRepository names and sourceRefs with similar repo switching patterns.

Suggested labels

base-cluster

Suggested reviewers

• tasches
• marvinWolff
• teutonet-bot

Poem

🐰 A rabbit hops through Helm repos with glee,
From grafana to grafana-community!
Tempo charts dance in their new spring home,
With conditions refined, through monitoring they roam.
✨ Sources shift, configurations align—
A cleaner tracing setup, hop-hop-fine! 🐇

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: migrating the Grafana Tempo chart source from the grafana repository to grafana-community repository, which involves updating the Helm repository configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/base-cluster/migrate-tempo-repo

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request correctly migrates the Grafana Tempo Helm chart to its new repository URL. The changes are mostly accurate, but I've identified an opportunity to improve the precision of a related Helm repository condition in values.yaml. My feedback includes a suggestion to refine this condition to prevent the creation of unnecessary resources.

[Copilot]

Pull request overview

This PR migrates the Grafana Tempo helm chart from the deprecated grafana helm repository to the new grafana-community helm repository, as referenced in grafana-community/helm-charts#2.

Changes:

• Moved tempo chart from grafana helm repository to new grafana-community helm repository
• Updated template reference in grafana-tempo.yaml to use the new repository name
• Modified repository conditions to separate grafana and grafana-community concerns

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
charts/base-cluster/values.yaml	Added new grafana-community helm repository configuration with tempo chart, updated grafana repository condition
charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml	Updated helm chart spec to reference grafana-community repository instead of grafana

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.