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

[teutonet-bot]

🤖 I have created a release beep boop

9.7.1 (2026-04-01)

Bug Fixes

• t8s-cluster/workload-cluster: adjust cilium healthChecks (#2038) (c23830e)

Miscellaneous Chores

• t8s-cluster/workload-cluster: move the updateStrategy -> strategy (c23830e)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

Release Notes – v9.7.1

• Bug Fixes

  • Adjusted Cilium health checks configuration in workload cluster to resolve issues.

• Chores

  • Updated workload cluster configuration parameter settings.

[coderabbitai]

Warning

Rate limit exceeded

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

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 22 minutes and 34 seconds.

⌛ 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: 44d58599-0e70-4c7e-8559-92a5e305832e

📥 Commits

Reviewing files that changed from the base of the PR and between 4c31aeb and 7c6bcd2.

📒 Files selected for processing (2)

• charts/t8s-cluster/Chart.yaml
• charts/t8s-cluster/README.md

📝 Walkthrough

Walkthrough

This pull request bumps the t8s-cluster Helm chart version from 9.7.0 to 9.7.1 and adds a corresponding changelog entry. Three files were updated: the release manifest, the chart metadata, and the chart CHANGELOG.

Changes

Cohort / File(s)	Summary
Release Manifest .github/release-please/manifest.json	Bumped charts/t8s-cluster entry from 9.7.0 → 9.7.1.
Chart Metadata charts/t8s-cluster/Chart.yaml	Incremented Helm chart version from 9.7.0 → 9.7.1.
Changelog charts/t8s-cluster/CHANGELOG.md	Added release notes for 9.7.1 (2026-04-01): Cilium healthChecks adjustment and updateStrategy → strategy chore for workload-cluster.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore(main): [bot] release t8s-cluster:9.6.0 #1945: Similar release artifacts updated for t8s-cluster (manifest, Chart.yaml, CHANGELOG).
• chore(main): [bot] release t8s-cluster:9.7.0 #2009: Prior t8s-cluster release PR that introduced the earlier 9.7.0 changes.
• chore(main): [bot] release t8s-cluster:9.3.1 #1502: Another release PR touching the same chart metadata and changelog.

Suggested labels

autorelease: tagged

Suggested reviewers

• tasches
• cwrau
• marvinWolff

Poem

🐇 A tiny bump, a tiny cheer,
Chart climbs from nine-seven, now nine-seven-one, clear.
Health checks tuned and fields set right,
I nibble changelogs through the night. ✨

🚥 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 PR title accurately describes the release operation for t8s-cluster version 9.7.1, matching the manifest, changelog, and chart version updates.
Linked Issues check	✅ Passed	The PR changes address both objectives from issue #2038: adjusting Cilium health checks (CHANGELOG entry) and moving updateStrategy to strategy field (CHANGELOG entry), with version bumps confirming release completion.
Out of Scope Changes check	✅ Passed	All changes are directly related to the 9.7.1 release and align with objectives in issue #2038; no unrelated modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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

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

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 represents an automated release of the t8s-cluster Helm chart, advancing its version to 9.8.0. The update incorporates a range of new features that enhance cluster management, security, and scalability, alongside several bug fixes that improve stability and configuration accuracy.

Highlights

• Features: Added staff authentication and RBAC for teuto staff.
• Features: Enabled kubeProxy replacement for Cilium and audit logging for the cluster.
• Features: Introduced new management cluster capabilities including adding 'compute-plane' role labels to nodes, cluster-autoscaler deployment, and quotas.
• Features: Implemented autoscaling and made API server resources configurable.
• Bug Fixes: Fixed missing security group rules for Cilium Hubble and adjusted test Helm repositories.
• Bug Fixes: Addressed issues with replicas type checking and migrated extraArgs type to string for workload clusters.
• Bug Fixes: Ensured nodePools only allow valid Kubernetes names and used plain values for autoscaling.

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.

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@charts/t8s-cluster/CHANGELOG.md`:
- Line 13: Update the changelog entry that currently reads "add quotas fied to
cluster" to correct the typo to "add quotas field to cluster" in the release
notes line containing that exact phrase; ensure the corrected entry preserves
the rest of the line (PR and commit links) unchanged.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a87bbf35-2442-46ec-a7c6-843db77434fd

📥 Commits

Reviewing files that changed from the base of the PR and between b5d116d and c3e129f.

📒 Files selected for processing (3)

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

[gemini-code-assist]

Code Review

This pull request automates the release of t8s-cluster version 9.8.0. The changes correctly update version numbers in manifest.json and Chart.yaml, and generate a new changelog entry. However, I've noticed a couple of issues. Firstly, the release date in charts/t8s-cluster/CHANGELOG.md and the pull request description is set to a future date (2026-03-20), which should be corrected. Secondly, in charts/t8s-cluster/Chart.yaml, one of the sources URLs still points to the tag of the previous version (v9.7.0) and should be updated to point to the new version's tag.

[teutonet-bot]

🤖 Created releases:

• t8s-cluster-v9.7.1

🌻