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

[teutonet-bot]

🤖 I have created a release beep boop

10.0.0 (2025-10-23)

⚠ BREAKING CHANGES

• base-cluster/backup: add k8up provider (#1751)

Features

• base-cluster/backup: add k8up provider (#1751) (0f36225)

Bug Fixes

• base-cluster/kyverno: change kubectl image (#1734) (cb42f26)
• base-cluster: conditions must the true, not just truthy (#1738) (7f46f4e)
• base-cluster: migrate promtail leftovers to alloy (#1720) (8b7d062)

Miscellaneous Chores

• base-cluster/external-dns: migrate domainFilters syntax (#1681) (51a42a2)
• base-cluster/kdave: remove kdave (#1724) (723c049)
• base-cluster/logs: only delete volumes on deletion (#1721) (36b657a)
• base-cluster/logs: optimize volume chown; this speeds up startup (36b657a)
• base-cluster/traces: delete tempo volumes on deletion (#1722) (0afce96)
• base-cluster: use upstream kubectl image instead of rancher (#1718) (d4daf94)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

Release Notes - Version 10.0.0

• Breaking Changes

  • base-cluster/backup provider modifications require attention during upgrade.

• New Features

  • base-cluster/backup enhancements.

• Bug Fixes

  • Kyverno configuration improvements.
  • kubectl image handling optimizations.
  • Boolean condition evaluation corrections.
  • Promtail migration cleanup.
  • Tempo volume deletion fixes.

• Chores

  • Infrastructure syntax and dependency updates.

[coderabbitai]

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 24 minutes and 16 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 42dd719 and 042483d.

📒 Files selected for processing (1)

• charts/base-cluster/Chart.yaml (3 hunks)

Walkthrough

Bumps the charts/base-cluster Helm chart to version 10.0.0 by updating the release manifest and Chart.yaml, and adds a new 10.0.0 changelog entry listing breaking changes, features, bug fixes, and chores.

Changes

Cohort / File(s)	Summary
Release manifest .github/release-please/manifest.json	Updated base-cluster version from 9.4.0 → 10.0.0; other manifest entries unchanged.
Chart metadata charts/base-cluster/Chart.yaml	Bumped chart version from 9.4.0 → 10.0.0. No exported/public entity declarations changed.
Changelog charts/base-cluster/CHANGELOG.md	Added 10.0.0 release notes (BREAKING CHANGES, Features, Bug Fixes, Miscellaneous Chores) and retained the 9.4.0 entry as previous release.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore(main): [bot] release base-cluster:9.1.0 #1628 — Performs the same base-cluster release file updates (Chart.yaml version bump and manifest/changelog edits).
• chore(main): [bot] release base-cluster:9.2.0 #1648 — Modifies the same release metadata for charts/base-cluster (manifest.json, Chart.yaml, CHANGELOG.md).
• chore(main): [bot] release base-cluster:9.3.0 #1657 — Another release update touching manifest and Chart.yaml for base-cluster.

Suggested labels

autorelease: tagged

Suggested reviewers

• tasches
• cwrau
• marvinWolff

Poem

🐰 I hopped the version up to ten,
Changelogs scrawled with careful pen.
Manifests nudged and charts aligned,
A tidy bump — release defined. 🥕

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 pull request title "chore(main): [bot] release base-cluster:10.0.0" clearly and concisely describes the primary change in the changeset. It follows conventional commit format with the "chore" type and directly communicates that this is a release of base-cluster version 10.0.0. The changes confirm this: the version is bumped from 9.4.0 to 10.0.0 across the manifest, CHANGELOG, and Chart.yaml. The title is specific enough to understand the main change when scanning PR history, with no vague language or misleading information.
Linked Issues Check	✅ Passed	The linked issue #1734 regarding the kyverno kubectl image change is directly referenced in the CHANGELOG.md updates under the Bug Fixes section as "base-cluster/kyverno: change kubectl image (refs #1734, commit cb42f26)". This release PR aggregates the implementation from that issue and appropriately documents it in the v10.0.0 changelog, indicating that the requirements to allow explicit specification of the kubectl image repository and tag, and to consolidate chart image annotations, are included in this release.
Out of Scope Changes Check	✅ Passed	All changes in this PR are directly related to the release process and are in-scope. The version bumps in manifest.json and Chart.yaml (9.4.0 → 10.0.0) and the CHANGELOG.md updates documenting new version 10.0.0 are the expected and appropriate changes for a Release Please automated release PR. The various implementation changes referenced in the CHANGELOG (kyverno, backup, external-dns, etc.) are already implemented in the codebase and are appropriately being documented as part of this release version.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/base-cluster/README.md (1)

3516-3598: Clarify what values dns.zones expects.

external-dns typically wants provider-specific zone identifiers (e.g. Cloudflare zone IDs), which differ from the domain names that stay in dns.domains. Without spelling that out here, readers can easily feed the wrong values and zone filtering will fail silently. Please explain the expected format and add a short example for Cloudflare or whichever provider you’ve validated.

-| - [zones](#dns_zones )       | No      | array of string | No         | -          | -                                                                                                           |
+| - [zones](#dns_zones )       | No      | array of string | No         | -          | List of provider-specific zone identifiers (e.g. Cloudflare zone IDs); falls back to domains if omitted    |

And extend the section below with a brief example showing the difference between domains (FQDNs) and zones (IDs) for at least one provider.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1126769 and 29cc147.

📒 Files selected for processing (2)

• charts/base-cluster/Chart.yaml (2 hunks)
• charts/base-cluster/README.md (6 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-07-24T09:55:53.655Z

Learnt from: cwrau
PR: teutonet/teutonet-helm-charts#1601
File: charts/base-cluster/templates/dns/external-dns.yaml:30-32
Timestamp: 2025-07-24T09:55:53.655Z
Learning: In charts/base-cluster/templates/dns/external-dns.yaml, the dns.provider field in values.yaml has always been expected to be a map format (e.g., `{ cloudflare: {} }`), never a string format. The template correctly uses `{{ .Values.dns.provider | keys | first }}` to extract the provider name from the map keys.

Applied to files:

• charts/base-cluster/README.md

⏰ 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). (2)

• GitHub Check: update metadata file for release
• GitHub Check: lint helm chart (base-cluster)

[coderabbitai]

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 1b3a1e4 and 159189a.

📒 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 (2)

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

⏰ 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). (2)

• GitHub Check: Update release-please config file for a possibly new chart
• GitHub Check: update metadata file for release

[teutonet-bot]

🤖 Created releases:

• base-cluster-v10.0.0

🌻