Skip to content

chore(main): [bot] release base-cluster:10.1.2#1841

Merged
teutonet-bot merged 4 commits intomainfrom
release-please--branches--main--components--base-cluster
Dec 5, 2025
Merged

chore(main): [bot] release base-cluster:10.1.2#1841
teutonet-bot merged 4 commits intomainfrom
release-please--branches--main--components--base-cluster

Conversation

@teutonet-bot
Copy link
Copy Markdown
Contributor

@teutonet-bot teutonet-bot commented Nov 28, 2025

🤖 I have created a release beep boop

10.1.2 (2025-12-05)

Bug Fixes

  • base-cluster/monitoring: move imageRenderer config to correct place (#1860) (5e2e9f5)
  • base-cluster: set default value for kube-janitor to own repo (#1857) (82b78e5)

Miscellaneous Chores

  • base-cluster/dependencies: update docker.io/grafana/grafana-image-renderer docker tag to v5 (#1822) (b9b16d7)
  • base-cluster/dependencies: update helm release alloy to v1.5.0 (#1855) (a157f21)
  • base-cluster/dependencies: update helm release kube-prometheus-stack to v79.11.0 (#1850) (94e7e00)
  • base-cluster/dependencies: update helm release kube-prometheus-stack to v79.9.0 (#1842) (a834e6d)
  • base-cluster/dependencies: update helm release reflector to v9.1.42 (#1854) (b9a042a)
  • base-cluster/dependencies: update helm release tempo-distributed to v1.57.0 (#1849) (c78f7d2)
  • base-cluster/ingress: update gateway api (#1843) (96a4b76)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

  • Bug Fixes

    • Fixed imageRenderer configuration placement in monitoring
    • Set default value for kube-janitor component
  • Chores

    • Updated multiple component versions: Grafana Image Renderer (v5), Alloy (v1.5.0), Kube Prometheus Stack (v79.11.0), Reflector (v9.1.42), and Tempo Distributed (v1.57.0)
    • Updated Gateway API

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Nov 28, 2025

Warning

Rate limit exceeded

@teutonet-bot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 32 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.

📥 Commits

Reviewing files that changed from the base of the PR and between 9d11134 and 0896b5f.

📒 Files selected for processing (2)
  • charts/base-cluster/Chart.yaml (4 hunks)
  • charts/base-cluster/README.md (2 hunks)

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Bump of charts/base-cluster from 10.1.1 to 10.1.2; release manifest and Chart.yaml updated and a new CHANGELOG entry added documenting bug fixes and multiple dependency updates.

Changes

Cohort / File(s) Summary
Base-cluster release metadata & changelog
​.github/release-please/manifest.json, charts/base-cluster/Chart.yaml, charts/base-cluster/CHANGELOG.md
Bumped chart version 10.1.110.1.2 in manifest and Chart.yaml; added CHANGELOG entry for 10.1.2 listing bug fixes (moved imageRenderer config, set kube-janitor default) and dependency updates (grafana-image-renderer tag v5, alloy v1.5.0, kube-prometheus-stack v79.x, reflector v9.1.42, tempo-distributed v1.57.0) and ingress gateway API update.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Focus areas:
    • charts/base-cluster/Chart.yaml — verify version bump only
    • .github/release-please/manifest.json — manifest entry consistency
    • charts/base-cluster/CHANGELOG.md — correct changelog content and formatting

Possibly related PRs

Suggested labels

autorelease: tagged

Suggested reviewers

  • tasches
  • marvinWolff
  • cwrau

Poem

🐰 A quiet hop, a tiny cheer,
Chart nudged forward, version clear.
Changelog notes and deps in line,
I twitch my nose — release is fine. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: a bot-generated release PR for base-cluster v10.1.2, which matches the version bump changes across all modified files.
Linked Issues check ✅ Passed The PR changelog includes the bug fix from #1860 (move imageRenderer config to correct place) and addresses the linked issue's requirement to reorganize monitoring configuration.
Out of Scope Changes check ✅ Passed All changes are in-scope: version bumps in manifest, chart descriptor, and changelog entries document the release with referenced dependency updates and bug fixes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

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

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @teutonet-bot, I'm Gemini Code Assist1! 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 marks the release of version 11.0.0 for the base-cluster Helm chart. This significant update integrates a multitude of new features, critical bug fixes, and extensive dependency upgrades across core cluster components. The changes aim to enhance the chart's functionality, improve stability, and provide more flexible configuration options for various services like backup, monitoring, ingress, and security.

Highlights

  • Major Version Bump to 11.0.0: This release introduces several breaking changes and significant new features, warranting a major version increment for the base-cluster Helm chart.
  • Backup System Enhancement: Introduced k8up as a new backup provider, offering more robust backup capabilities.
  • Monitoring and Alerting Improvements: Enhanced Alertmanager with new receiver and route configuration options, migrated Promtail to Alloy for logging, and added various monitoring-related features and fixes.
  • Ingress Controller Flexibility: Added Traefik as an ingress controller option and made it the default, alongside other ingress-related updates.
  • Dependency Updates: Numerous dependencies across various components (e.g., common docker tag, kubectl, curl, flux-cli, grafana-image-renderer, external-dns, grafana-tempo, alloy, descheduler, kube-prometheus-stack, kyverno, loki, metrics-server, oauth2-proxy, reflector, tempo-distributed, tetragon, traefik, trivy-operator, velero) have been updated to their latest versions.
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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request is an automated release for base-cluster version 11.0.0. The changes include updating the version in manifest.json and Chart.yaml, and adding a new entry to CHANGELOG.md.

My review has identified two issues:

  1. The CHANGELOG.md is cluttered with commits from previous bot releases, which makes it hard to read. I've suggested a configuration change for release-please to filter these out.
  2. The sources URL in Chart.yaml has not been updated and still points to the previous version tag. This should be corrected to point to the new v11.0.0 tag.

These are likely configuration issues with the release-please bot that should be addressed to ensure clean and accurate releases in the future.

Comment thread charts/base-cluster/Chart.yaml Outdated
Comment thread charts/base-cluster/CHANGELOG.md Outdated
@teutonet-bot teutonet-bot changed the title chore(main): [bot] release base-cluster:11.0.0 chore(main): [bot] release base-cluster:10.1.2 Dec 1, 2025
@teutonet-bot teutonet-bot force-pushed the release-please--branches--main--components--base-cluster branch 9 times, most recently from 2f0fd6b to 2730a28 Compare December 5, 2025 09:25
Copy link
Copy Markdown

@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: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fcfa8e6 and 2730a28.

📒 Files selected for processing (3)
  • .github/release-please/manifest.json (1 hunks)
  • charts/base-cluster/CHANGELOG.md (1 hunks)
  • charts/base-cluster/Chart.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • .github/release-please/manifest.json
🧰 Additional context used
🧠 Learnings (3)
📚 Learning: 2025-07-24T09:41:28.072Z
Learnt from: cwrau
Repo: teutonet/teutonet-helm-charts PR: 1604
File: charts/base-cluster/templates/monitoring/metrics-server/metrics-server.yaml:20-21
Timestamp: 2025-07-24T09:41:28.072Z
Learning: The official kubernetes-sigs/metrics-server Helm chart pins the image tag to a specific version in its values.yaml by default, ensuring reproducible deployments without requiring explicit tag specification in consuming charts.

Applied to files:

  • charts/base-cluster/Chart.yaml
📚 Learning: 2025-07-24T09:41:28.072Z
Learnt from: cwrau
Repo: teutonet/teutonet-helm-charts PR: 1604
File: charts/base-cluster/templates/monitoring/metrics-server/metrics-server.yaml:20-21
Timestamp: 2025-07-24T09:41:28.072Z
Learning: The kubernetes-sigs/metrics-server Helm chart uses `v{{ .Chart.AppVersion }}` as the default image tag when `image.tag` is empty, which provides pinned versioning through the chart's AppVersion rather than using floating tags like "latest".

Applied to files:

  • charts/base-cluster/Chart.yaml
📚 Learning: 2025-07-24T09:49:40.961Z
Learnt from: cwrau
Repo: teutonet/teutonet-helm-charts PR: 1602
File: charts/base-cluster/templates/monitoring/kube-prometheus-stack/oauth-proxy.yaml:38-40
Timestamp: 2025-07-24T09:49:40.961Z
Learning: Official Helm charts like oauth2-proxy manage image versioning automatically through their Chart.yaml appVersion field, making manual tag pinning in consumer values unnecessary and potentially harmful. The chart version itself provides reproducibility by ensuring the correct image tag is used.

Applied to files:

  • charts/base-cluster/Chart.yaml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: lint helm chart (base-cluster)
🔇 Additional comments (1)
charts/base-cluster/CHANGELOG.md (1)

3-20: Changelog entry looks good.

The new 10.1.2 entry is properly formatted with all referenced issues and commit hashes. The bug fixes and dependency updates are clearly documented.

Comment thread charts/base-cluster/Chart.yaml Outdated
@teutonet-bot teutonet-bot force-pushed the release-please--branches--main--components--base-cluster branch from b1837e3 to 9d11134 Compare December 5, 2025 10:09
@teutonet-bot teutonet-bot added this pull request to the merge queue Dec 5, 2025
Merged via the queue into main with commit b21ccab Dec 5, 2025
19 checks passed
@teutonet-bot teutonet-bot deleted the release-please--branches--main--components--base-cluster branch December 5, 2025 10:24
@teutonet-bot
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

2 participants