chore(main): [bot] release t8s-cluster:9.9.0

[teutonet-bot]

🤖 I have created a release beep boop

9.9.0 (2026-04-30)

Features

• t8s-cluster/management-cluster: allow auditing of kcp clusters (opt-in) (#2039) (3387520)
• t8s-cluster/management-cluster: enable etcd backups (#2042) (449eb0a)
• t8s-cluster/management-cluster: enable MutatingAdmissionPolicy (#2046) (587e2d9)
• t8s-cluster/management-cluster: exluce selfsubjectaccessreviews from audit (#2094) (f1be84e)
• t8s-cluster: warn about PodSecurityStandard violations by default (#2078) (1a0c9c1)

Miscellaneous Chores

• t8s-cluster/dependencies: update cilium docker tag to v1.19.2 (#2014) (a5aafb7)
• t8s-cluster/dependencies: update cilium docker tag to v1.19.3 (#2069) (e079cb6)
• t8s-cluster/dependencies: update common docker tag to v2 (#2075) (f3e8137)
• t8s-cluster/dependencies: update helm release cluster-autoscaler to v9.55.1 (#2015) (5383b17)
• t8s-cluster/dependencies: update helm release cluster-autoscaler to v9.56.0 (#2063) (ecc6700)
• t8s-cluster/dependencies: update registry.k8s.io/etcd docker tag to v3.6.10 (#2036) (a47ee18)

---

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 55 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: e2fcc66b-9cac-48c6-a52f-4bd715e51df2

📥 Commits

Reviewing files that changed from the base of the PR and between 92686ec and f6f4dde.

📒 Files selected for processing (4)

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

📝 Walkthrough

Walkthrough

Version bump for the t8s-cluster Helm chart from 9.8.0 to 9.9.0, including updates to the release-please manifest, Chart.yaml version field, and a new changelog entry documenting new management-cluster capabilities and dependency updates.

Changes

Cohort / File(s)	Summary
t8s-cluster v9.9.0 Release .github/release-please/manifest.json, charts/t8s-cluster/Chart.yaml, charts/t8s-cluster/CHANGELOG.md	Version bump from 9.8.0 to 9.9.0, including manifest updates, chart metadata, and changelog entry documenting new management-cluster capabilities (auditing of kcp clusters, etcd backups, MutatingAdmissionPolicy enablement, audit filters), PodSecurityStandard warnings, and dependency updates for Cilium, common, cluster-autoscaler, and etcd.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• #2044: Similar release bump for t8s-cluster (9.7.1→9.8.0) modifying the same manifest, Chart.yaml, and changelog files.
• #2009: Prior t8s-cluster release bump (9.6→9.7) updating the same release artifact files.
• #1755: Related t8s-cluster release bump modifying Chart.yaml, CHANGELOG.md, and release-please manifest.

Suggested labels

autorelease: tagged

Suggested reviewers

• tasches
• cwrau
• marvinWolff

Poem

🐰 Bumped up from eight to nine,
New features shine so fine!
Audits, backups, policies aligned,
Another cluster release, by design! ✨

🚥 Pre-merge checks | ✅ 5

✅ 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 clearly and accurately describes the main purpose of the PR: releasing t8s-cluster version 9.9.0.
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.

_{✏️ 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--t8s-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 55 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 t8s-cluster chart version from 9.8.0 to 9.9.0 across the manifest, changelog, and chart metadata, introducing a new feature for kcp cluster auditing. Feedback indicates that the source URL in Chart.yaml still references the old v9.8.0 tag and should be updated to maintain consistency with the new release version.

[gemini-code-assist]

The version has been bumped to 9.9.0, but the source URL on line 18 still points to the v9.8.0 tag. It should be updated to v9.9.0 to ensure that metadata tools like ArtifactHub point to the correct source code for this release. When updating, ensure the 'v' prefix is maintained for the Git tag as per repository standards.

References

1. When validating a semver version against tags in a Git repository, ensure the validation logic correctly handles tags that are prefixed with 'v' (e.g., 'v1.4.0') when the specified version is not (e.g., '1.4.0').