chore(main): [bot] release common:1.8.0

[teutonet-bot]

🤖 I have created a release beep boop

1.8.0 (2025-12-09)

Features

• common/helm: add option to set namespace of HelmRepository (#1757) (6efd87b)
• common/images: add template for pullPolicy (#1381) (fac4246)
• common/telemetry: abstract telemetry config to allow typed usage (#1346) (5e5742f)
• common/telemetry: add telemetry-collector as a generic service name (#1432) (fdf3b21)
• common: add kube-apiserver networkpolicy helper (#1413) (58ed072)
• common: add statefulset recreate job (#1723) (6f40d20)
• common: centralise helmRepositories templating (#1844) (31b1629)

Miscellaneous Chores

• common/dependencies: update helm release common to v2.27.0 (#1389) (9e7587f)
• common/dependencies: update helm release common to v2.31.4 (#1532) (7df033f)
• common/docs: set vim modeline (#1273) (322db3f)
• common: add documentation about template usage (#1426) (638add8)
• main: [bot] release common:1.3.0 (#1077) (ff40004)
• main: [bot] release common:1.4.0 (#1385) (cc9cc7f)
• main: [bot] release common:1.5.0 (#1391) (036125b)
• main: [bot] release common:1.6.0 (#1766) (f870cda)
• main: [bot] release common:1.7.0 (#1787) (3014b2c)

---

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 or files that can be reviewed per hour. Please wait 19 minutes and 32 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 3014b2c and e558bc3.

📒 Files selected for processing (4)

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

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

✨ 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--common

---

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 @teutonet-bot, 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 is an automated release of version 1.8.0 for the common Helm chart. This update bundles several new features, including enhanced HelmRepository configuration, flexible image pullPolicy templating, and refined telemetry settings. It also introduces new utilities like a kube-apiserver network policy helper and a StatefulSet recreate job, alongside centralizing Helm repository templating and updating key dependencies.

Highlights

• New Helm Chart Release: The common Helm chart has been released as version 1.8.0, incorporating a collection of new features and updates.
• HelmRepository Namespace Option: An option has been added to allow setting the namespace for HelmRepository configurations.
• Image Pull Policy Template: A new template for pullPolicy has been introduced for images, providing more flexibility.
• Telemetry Configuration Enhancements: Telemetry configuration has been abstracted for typed usage, and telemetry-collector is now a generic service name.
• Kube-apiserver Network Policy Helper: A helper for kube-apiserver network policies has been added to simplify network access control.
• StatefulSet Recreate Job: A job to recreate StatefulSets has been included, likely for easier updates or recovery.
• Centralized Helm Repositories Templating: The templating for Helm repositories has been centralized for consistency and easier management.
• Dependency Updates: The common Helm release dependencies have been updated to versions v2.27.0 and v2.31.4.
• Documentation Update: Documentation regarding template usage has been added to the common chart.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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

[gemini-code-assist]

Code Review

This pull request is an automated release for common:1.8.0. The changes correctly bump the version in manifest.json and Chart.yaml, and update the CHANGELOG.md. I've added a comment to the changelog regarding duplicated entries from previous releases, which might be caused by the release automation configuration and could be improved for clarity.

[gemini-code-assist]

The changelog for version 1.8.0 appears to include changes that were already part of previous releases. This creates redundancy and makes it difficult to understand what is new in this version. For example, several features listed under 1.8.0 also appear in the release notes for versions 1.7.0, 1.6.0, 1.5.0, 1.4.0, and 1.3.0.

Each release section in the changelog should ideally only contain the changes specific to that release. This might indicate a misconfiguration in the release-please setup that could be worth investigating to ensure the changelog remains clear and accurate.