chore(main): [bot] release base-cluster:12.0.0

[teutonet-bot]

🤖 I have created a release beep boop

12.0.0 (2026-04-30)

⚠ BREAKING CHANGES

• base-cluster/trivy: set trivy disabled by default (#2100)
• base-cluster: remove unnecessary enabled field for deadMansSwitch (#1652)
• base-cluster: migrate kube-janitor to k8s-ttl-controller (#2091)

Features

• base-cluster: remove unnecessary enabled field for deadMansSwitch (#1652) (b1bc781)

Bug Fixes

• base-cluster/cert-manager: add new line to fix breaking yaml file (#2010) (90ab5b5)
• base-cluster: add missing descheduler config (#2092) (6ecbbae)

Miscellaneous Chores

• base-cluster/dependencies: update docker.io/curlimages/curl:8.19.0 docker digest to c03110c (#2102) (5de17f0)
• base-cluster/dependencies: update docker.io/fluxcd/flux-cli docker tag to v2.8.6 (#2093) (6a2a884)
• base-cluster/dependencies: update helm release kube-prometheus-stack to v83.7.0 (#2096) (aa0845b)
• base-cluster/dependencies: update helm release reflector to v10.0.37 (#2097) (3c2a070)
• base-cluster/trivy: set trivy disabled by default (#2100) (39e7f6a)
• base-cluster: migrate kube-janitor to k8s-ttl-controller (#2091) (5ee6289)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Rate limit exceeded

@teutonet-bot has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 43 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ 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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f1e5a52f-d30d-4f95-b2e7-c77af497c4fc

📥 Commits

Reviewing files that changed from the base of the PR and between 9d6e9f5 and 7231047.

📒 Files selected for processing (4)

• .github/release-please/manifest.json
• charts/base-cluster/CHANGELOG.md
• charts/base-cluster/Chart.yaml
• charts/base-cluster/README.md

📝 Walkthrough

Walkthrough

Bumps the charts/base-cluster Helm chart from 11.2.0 to 12.0.0; updates .github/release-please/manifest.json and charts/base-cluster/Chart.yaml; adds a charts/base-cluster/CHANGELOG.md entry for v12.0.0 documenting breaking changes, features, bug fixes, and chores.

Changes

Cohort / File(s)	Summary
base-cluster release metadata ​.github/release-please/manifest.json, charts/base-cluster/Chart.yaml, charts/base-cluster/CHANGELOG.md	Bumped charts/base-cluster version 11.2.0 → 12.0.0; added v12.0.0 changelog entry noting BREAKING CHANGES (removal of deadMansSwitch.enabled, migration from kube-janitor → k8s-ttl-controller), feature/bugfix/chore bullets, and dependency image/tag updates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore(main): [bot] release base-cluster:11.1.1 #2023: Similar chart release artifact changes for charts/base-cluster (Chart.yaml, CHANGELOG, manifest).
• chore(base-cluster)!: migrate kube-janitor to k8s-ttl-controller #2091: PR that implements the kube-janitor → k8s-ttl-controller migration referenced in the changelog.
• chore(main): [bot] release base-cluster:8.0.0 #1398: Related release metadata edits for charts/base-cluster (version bump, changelog, manifest).

Suggested labels

autorelease: tagged

Suggested reviewers

• tasches
• cwrau
• marvinWolff

Poem

🐇 I nudged a chart from eleven to twelve,
My paws in changelogs happily delve.
A manifest tweak, a version new —
Pipelines hum and seeds will stew.
🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: a release bump of the base-cluster chart to version 12.0.0, which is directly reflected in all modified files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main--components--base-cluster

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 54 minutes and 43 seconds.}

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

[gemini-code-assist]

Code Review

This pull request updates the base-cluster Helm chart version from 11.2.0 to 11.2.1. The changes include updating the release manifest, adding a changelog entry for a bug fix regarding a missing descheduler configuration, and bumping the version in the Chart.yaml file. I have no feedback to provide.