chore: [bot] release: 1.3.0

[teutonet-bot]

🤖 I have created a release beep boop

1.3.0 (2025-11-25)

Features

• add hash for kube-root-ca.crt configmap to konnectivity-agent (#38) (9f4e977)
• add nix dev-shell (#51) (d6c6eb1)
• auto-generate the metadata.yaml instead of manually adjusting it (#42) (4a29346)
• update k8s dependencies + dependants (#41) (885dcb5)

Bug Fixes

• always create new titleCaser (#37) (bafb5a1)
• oidc jwks conformance (#39) (5925f36)
• use correct namespace for dev (#36) (7f5e3f4)

---

This PR was generated with Release Please. See documentation.

[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 represents the automated release of version 1.4.0 for the Cluster API hosted control plane provider. It integrates a substantial set of new features and critical bug fixes aimed at significantly improving the management, security, networking, and overall reliability of hosted Kubernetes control planes. Key enhancements include new CRDs for control plane templating, advanced audit and network policy configurations, robust ETCD management with S3 backup, and important dependency updates.

Highlights

• Enhanced Control Plane Management: Introduced the HostedControlPlaneTemplate CRD, implemented core HostedControlPlane service reconciliation, and improved control plane component deployment logic for greater flexibility and control.
• Improved Security and Networking: Added audit configuration options, authentication for audit webhooks, and comprehensive network policy support, including CiliumNetworkPolicies, to bolster security and network isolation.
• ETCD Management and Reliability: Implemented robust ETCD cluster management, enhanced certificate handling, and integrated S3 backup capabilities to ensure data durability and operational resilience.
• Dependency Updates and Bug Fixes: Updated Kubernetes dependencies to leverage the latest features and security patches, and addressed several critical issues, including OIDC JWKS conformance and kube-proxy configuration.

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, generated by a bot, prepares for the 1.4.0 release. It updates the version in the release-please manifest and adds a new section to the CHANGELOG.md. However, the generated changelog for 1.4.0 seems to incorrectly include commit history from all previous versions, making it redundant and hard to read. I've left a comment on the CHANGELOG.md file with details. This likely points to a misconfiguration in the release automation that should be addressed.

[teutonet-bot]

🤖 Created releases:

• v1.3.0

🌻