Skip to content

feat(base-cluster/monitoring): allow upsizing tempo storage#1448

Merged
cwrau merged 1 commit intomainfrom
feat/base-cluster/allow-tempo-ingester-storage-resizing
Jun 5, 2025
Merged

feat(base-cluster/monitoring): allow upsizing tempo storage#1448
cwrau merged 1 commit intomainfrom
feat/base-cluster/allow-tempo-ingester-storage-resizing

Conversation

@cwrau
Copy link
Member

@cwrau cwrau commented Apr 29, 2025

Summary by CodeRabbit

  • New Features
    • Added configurable persistent storage size for the tracing ingester component in monitoring settings.
  • Documentation
    • Updated configuration schema and default values to include the new persistence option for the tracing ingester.

Copilot AI review requested due to automatic review settings April 29, 2025 08:07
@cwrau cwrau enabled auto-merge April 29, 2025 08:07
@coderabbitai
Copy link

coderabbitai bot commented Apr 29, 2025

Walkthrough

The changes introduce a configurable persistent storage size for the tracing ingester component within the monitoring stack. This is achieved by updating the Helm chart template to accept a persistence size parameter, extending the values schema to validate this new property, and setting a default value in the configuration file. No changes were made to logic, exported entities, or other configuration sections beyond the tracing ingester persistence settings.

Changes

File(s) Change Summary
charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml Added a persistence block with a configurable size field to the ingester section, sourcing value from .Values.monitoring.tracing.ingester.persistence.size.
charts/base-cluster/values.schema.json Extended the schema for tracing.ingester to include an optional persistence object with a size property referencing the quantity type.
charts/base-cluster/values.yaml Added a persistence block with a default size of 10Gi under monitoring.tracing.ingester.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Helm Chart
    participant Kubernetes
    participant PersistentVolume

    User->>Helm Chart: Set tracing.ingester.persistence.size in values.yaml
    Helm Chart->>Kubernetes: Deploy Grafana Tempo with persistence config
    Kubernetes->>PersistentVolume: Provision volume of specified size
    Kubernetes->>Grafana Tempo Ingester: Attach persistent volume
Loading

Suggested reviewers

  • teutonet-bot

Poem

In the cluster where traces flow,
A new persistence block starts to grow.
Ten gigabytes, safe and sound,
For ingester data to be found.
Now logs and spans will never flee,
Thanks to storage—hoppily!
🐰✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 93d00aa and a9f5f2e.

📒 Files selected for processing (3)
  • charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml (1 hunks)
  • charts/base-cluster/values.schema.json (1 hunks)
  • charts/base-cluster/values.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • charts/base-cluster/values.yaml
  • charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml
  • charts/base-cluster/values.schema.json
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: wait-for-checks

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces the ability to upsize Tempo storage by adding a persistence configuration.

  • Added persistence configuration under the ingester section in the values.yaml file.
  • Updated the Grafana Tempo template to include persistence with the specified size.

Reviewed Changes

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

File Description
charts/base-cluster/values.yaml Added a persistence block for ingester with a default size of 10Gi
charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml Included a persistence block referencing the persistence size value
Files not reviewed (1)
  • charts/base-cluster/values.schema.json: Language not supported

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
charts/base-cluster/values.schema.json (1)

967-976: Consistency with other persistence schema definitions
Unlike existing persistence schemas for monitoring.prometheus, alertmanager, and loki, this new tracing.ingester.persistence block only exposes a size property and does not allow configuring storageClass. Consider adding a storageClass (or storageClassName) property to this schema to align with the other persistence blocks and enable users to override the storage class for Tempo ingester volumes.

charts/base-cluster/values.yaml (1)

341-342: Clarify persistence toggling and storage class overrides
The tracing.ingester.persistence block defines only a size, whereas other charts (e.g., Grafana) also include enabled and storageClassName flags. If you intend to keep persistence always on, document this behavior in README. Otherwise, you may want to introduce an enabled flag or allow specifying a storageClassName for greater flexibility.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd8d39e and 93d00aa.

📒 Files selected for processing (3)
  • charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml (1 hunks)
  • charts/base-cluster/values.schema.json (1 hunks)
  • charts/base-cluster/values.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: generateDiffCommentBody
  • GitHub Check: check licenses
  • GitHub Check: lint helm chart (base-cluster)
  • GitHub Check: wait-for-checks
🔇 Additional comments (1)
charts/base-cluster/templates/monitoring/tracing/grafana-tempo.yaml (1)

25-26: Verify alignment with the Bitnami Grafana-Tempo chart’s expected values
The template injects persistence.size under ingester, but does not set persistence.enabled or persistence.storageClass. Confirm that the upstream Bitnami chart’s default for ingester.persistence.enabled is true (so persistence is actually enabled) and that it does not require a storageClass key. Also double-check the indentation to ensure the block nests correctly under ingester.

@cwrau cwrau force-pushed the feat/base-cluster/allow-tempo-ingester-storage-resizing branch from 93d00aa to a9f5f2e Compare June 5, 2025 08:34
@cwrau cwrau added this pull request to the merge queue Jun 5, 2025
Merged via the queue into main with commit db1a742 Jun 5, 2025
23 of 32 checks passed
@cwrau cwrau deleted the feat/base-cluster/allow-tempo-ingester-storage-resizing branch June 5, 2025 08:56
github-merge-queue bot pushed a commit that referenced this pull request Jun 6, 2025
🤖 I have created a release *beep* *boop*
---


##
[8.1.0](base-cluster-v8.0.0...base-cluster-v8.1.0)
(2025-06-06)


### Features

* **base-cluster/monitoring:** allow upsizing tempo storage
([#1448](#1448))
([db1a742](db1a742))
* **base-cluster/monitoring:** also read secrets for datasources
([#1479](#1479))
([83ba8bd](83ba8bd))
* **base-cluster/monitoring:** configure service graph for grafana
([#1422](#1422))
([8d4bb4c](8d4bb4c))
* **base-cluster/monitoring:** set code challenge for grafana
([#1500](#1500))
([aa803da](aa803da))
* **base-cluster/monitoring:** set code_challenge_method for
oauth2-proxy
([#1496](#1496))
([b252cd7](b252cd7))


### Bug Fixes

* **base-cluster:** this prevents the user from installing this under
another name
([#1418](#1418))
([f4807e8](f4807e8))


### Miscellaneous Chores

* **base-cluster/docs:** update flux helmrelease command to update CRDs
([#1421](#1421))
([a8fd535](a8fd535))
* **base-cluster/monitoring:** remove unnecessary
open-telemetry-collector dashboard
([#1449](#1449))
([520e9e1](520e9e1))
* **base-cluster:** change descheduler syntax
([#1483](#1483))
([907bdae](907bdae))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
  - Enhanced monitoring with support for upsizing tempo storage.
- Enabled reading secrets for datasources and configuring the service
graph in Grafana.
- Added options to set the code challenge and code_challenge_method for
Grafana and oauth2-proxy.
- Introduced an optional persistence configuration for tracing ingester
storage size.

- **Bug Fixes**
- Resolved an issue preventing installation of the chart under
unintended names.

- **Chores**
  - Updated helmrelease command for CRD updates.
  - Removed an unnecessary dashboard and adjusted descheduler syntax.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants