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

[teutonet-bot]

🤖 I have created a release beep boop

9.5.0 (2026-01-15)

Features

• t8s-cluster/artifacthub: use centralised helmRepositories template (#1846) (73a41f9)
• t8s-cluster/cilium: enable kubeProxy replacement (#1815) (b3c412d)
• t8s-cluster/management-cluster: add cluster-autoscaler deployment (#1756) (5b6ead9)
• t8s-cluster/management-cluster: enable ImageVolume feature flag (#1786) (9676ee0)
• t8s-cluster/management-cluster: set apiServerLoadBalancer.provider via TeutonetesCloud (#1898) (6bf8889)
• t8s-cluster/management-cluster: switch to hcp (#1759) (303b0b6)
• t8s-cluster/management-cluster: use new KubeletEnsureSecretPulledImages feature gate (#1858) (40d7bef)
• t8s-cluster: migrate to CAPI v1beta2 (#1685) (dc5f071)

Bug Fixes

• t8s-cluster/autoscaler: these names are inside the workload cluster (#1877) (f345cea)
• t8s-cluster/management-cluster: leave out protocol if nil (#1837) (f370dac)
• t8s-cluster: only allow nodePools with valid k8s names (#1851) (b9431c5)

Miscellaneous Chores

• t8s-cluster/dependencies: update common docker tag to v1.6.0 (#1811) (b3b4c94)
• t8s-cluster/dependencies: update common docker tag to v1.7.0 (#1873) (71e062f)
• t8s-cluster/dependencies: update helm release cilium to v1.18.6 (#1894) (e1adc88)
• t8s-cluster/dependencies: update helm release cluster-autoscaler to v9.53.0 (#1856) (dc67fcd)
• t8s-cluster/dependencies: update helm release openstack-cloud-controller-manager to v2.34.1 (#1553) (e984d19)
• t8s-cluster/dependencies: update registry.k8s.io/etcd docker tag to v3.5.24 (#1793) (a5098e3)
• t8s-cluster/dependencies: update registry.k8s.io/etcd docker tag to v3.6.6 (#1813) (e07ffa7)
• t8s-cluster/dependencies: update registry.k8s.io/etcd docker tag to v3.6.7 (#1895) (cf1d3b4)
• t8s-cluster/flux: use centralised HelmRepositories instead of per-instance (#1758) (3deff65)

---

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 25 minutes and 36 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 3597db0 and 169e1b5.

📒 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

Bumps the t8s-cluster Helm chart from 9.4.1 to 9.5.0 by updating the release manifest and Chart.yaml, and appends a 9.5.0 changelog entry documenting Features, Bug Fixes, and Miscellaneous Chores.

Changes

Cohort / File(s)	Summary
Release metadata ​.github/release-please/manifest.json, charts/t8s-cluster/Chart.yaml	Chart version updated from 9.4.1 → 9.5.0.
Release notes / changelog charts/t8s-cluster/CHANGELOG.md	Appended 9.5.0 entry with Features, Bug Fixes, and Miscellaneous Chores (component updates and dependency bumps).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore(main): [bot] release t8s-cluster:9.4.0 #1680 — another release bump touching manifest.json, Chart.yaml, and CHANGELOG.md.
• chore(main): [bot] release t8s-cluster:9.3.1 #1502 — prior release update for the same chart and files.
• chore(main): [bot] release t8s-cluster:9.3.0 #1412 — earlier release-style changes for t8s-cluster (Chart.yaml and manifest updates).

Suggested labels

autorelease: tagged

Suggested reviewers

• tasches
• cwrau
• marvinWolff

Poem

🐰 A tiny hop, a tidy chart bump,
Version nudged up with a cheerful thump.
Changelog penned and metadata tuned,
I nibble a carrot while releases ballooned. 🥕✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title clearly and specifically identifies the primary change: a version release of the t8s-cluster Helm chart from 9.4.1 to 9.5.0, which matches the manifest and changelog updates.
Linked Issues check	✅ Passed	The PR addresses the linked issue #1877 by simplifying autoscaler configuration to treat names and resources as belonging to the workload cluster, avoiding management-cluster namespace references, as confirmed in changelog and PR objectives.
Out of Scope Changes check	✅ Passed	All changes are within scope: manifest.json version bump, Chart.yaml version update, and CHANGELOG.md entries documenting the 9.5.0 release with component updates directly related to linked issue #1877 and release objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.}

---

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/t8s-cluster/Chart.yaml (1)

18-18: Update source reference to reflect new chart version.

Line 18 still references the old tag t8s-cluster-v9.4.1 in the sources URL. For consistency and accurate documentation, this should be updated to t8s-cluster-v9.5.0.

Apply this diff to update the source reference:

-    - https://github.com/teutonet/teutonet-helm-charts/tree/t8s-cluster-v9.4.1/charts/t8s-cluster
+    - https://github.com/teutonet/teutonet-helm-charts/tree/t8s-cluster-v9.5.0/charts/t8s-cluster

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5b6ead9 and 2f42df0.

📒 Files selected for processing (3)

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

🔇 Additional comments (3)

.github/release-please/manifest.json (1)

1-1: Version bump correctly reflected in manifest.

The t8s-cluster chart version is correctly updated from 9.4.1 to 9.5.0, with all other chart versions unchanged. This aligns with the release intent.

charts/t8s-cluster/Chart.yaml (1)

21-21: Chart version bump to 9.5.0 looks good.

The version field is correctly updated to match the release.

charts/t8s-cluster/CHANGELOG.md (1)

3-9: Changelog entry for 9.5.0 is well-formed and accurate.

The new release section is correctly formatted, dated (2025-10-22), and documents the cluster-autoscaler deployment feature with appropriate issue and commit references. The previous 9.4.1 entry is properly preserved below.

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• 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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/t8s-cluster/Chart.yaml (1)

18-18: Consider updating the source URL to reference the new release tag.

The sources field on line 18 still references the old v9.4.1 release tag, while the chart version has been bumped to 9.5.0. Consider updating this to t8s-cluster-v9.5.0 to keep the reference current and consistent with the chart version. Line 19's reference to main is also appropriate and remains current.

Apply this diff to align the source URL with the new version:

-    - https://github.com/teutonet/teutonet-helm-charts/tree/t8s-cluster-v9.4.1/charts/t8s-cluster
+    - https://github.com/teutonet/teutonet-helm-charts/tree/t8s-cluster-v9.5.0/charts/t8s-cluster

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ea17e2f and 1eb90c7.

📒 Files selected for processing (3)

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

🚧 Files skipped from review as they are similar to previous changes (2)

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

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

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.

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.

📚 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/t8s-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/t8s-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/t8s-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 (t8s-cluster)

🔇 Additional comments (1)

charts/t8s-cluster/Chart.yaml (1)

21-21: Version bump looks correct.

The version field correctly updates from 9.4.1 to 9.5.0, matching the release notes and PR objectives.

[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 e4049b5 and cd7790d.

📒 Files selected for processing (3)

• .github/release-please/manifest.json (1 hunks)
• charts/t8s-cluster/CHANGELOG.md (1 hunks)
• charts/t8s-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/t8s-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/t8s-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/t8s-cluster/Chart.yaml

🪛 GitHub Actions: Lint Helm Charts

charts/t8s-cluster/Chart.yaml

[error] 1-1: Chart linting failed. 1 chart(s) linted, 1 chart(s) failed.

charts/t8s-cluster/CHANGELOG.md

[error] 1-1: Chart linting failed. 1 chart(s) linted, 1 chart(s) failed.

🔇 Additional comments (1)

charts/t8s-cluster/CHANGELOG.md (1)

3-31: LGTM! Comprehensive and well-structured changelog entry.

The 9.5.0 changelog entry is complete and well-formatted with proper issue references, commit hashes, and clear categorization of features, bug fixes, and chores. The documented changes align well with the PR objectives, including the autoscaler namespace fix (issue #1877), CAPI v1beta2 migration, and dependency updates. All entries follow the conventional commit format expected by release-please tooling.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @charts/t8s-cluster/Chart.yaml:
- Line 18: The Chart.yaml source URL is stale (points to
teutonet-helm-charts/tree/t8s-cluster-v9.4.1) while the chart version is 9.5.0;
update the URL in Chart.yaml to reference the matching tag t8s-cluster-v9.5.0 so
the source link matches the chart version.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd7790d and e8bbb7b.

📒 Files selected for processing (3)

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

🚧 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/t8s-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/t8s-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/t8s-cluster/Chart.yaml

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @charts/t8s-cluster/Chart.yaml:
- Line 18: Update the chart source URL to match the new release version by
replacing the reference "t8s-cluster-v9.4.1" with "t8s-cluster-v9.5.0" in the
Chart.yaml source entry so it aligns with the version on line 21.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e8bbb7b and f822d29.

📒 Files selected for processing (3)

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

🚧 Files skipped from review as they are similar to previous changes (2)

• charts/t8s-cluster/CHANGELOG.md
• .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/t8s-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/t8s-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/t8s-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). (2)

• GitHub Check: wait-for-checks
• GitHub Check: wait-for-checks

🔇 Additional comments (1)

charts/t8s-cluster/Chart.yaml (1)

21-21: LGTM! Version bump is appropriate.

The minor version bump from 9.4.1 to 9.5.0 correctly follows semantic versioning for the features, bug fixes, and dependency updates listed in the changelog.

[teutonet-bot]

🤖 Created releases:

• t8s-cluster-v9.5.0

🌻