Search code, repositories, users, issues, pull requests...

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

charts/t8s-cluster/ci/hcp-with-resources-values.yaml

charts/t8s-cluster/ci/cp-with-resources-values.yaml

coderabbitai · 2025-04-22T07:45:04Z

Walkthrough

The version for the t8s-cluster Helm chart was updated from 9.2.1 to 9.3.0 across relevant files. A changelog entry was added documenting four new features: adding RBAC for Teuto staff, enabling audit logging, customizable apiserver resource configurations, and a new pullPolicy template. The chart’s container images and license references were updated to newer versions and registries. The README schema was extended with resource requirements and security group rule enhancements.

Changes

File(s)	Change Summary
.github/release-please/manifest.json	Updated `charts/t8s-cluster` version from 9.2.1 to 9.3.0.
charts/t8s-cluster/Chart.yaml	Incremented chart version from 9.2.1 to 9.3.0; updated source URL; upgraded OpenStack Cinder CSI, cloud controller, and CSI images; removed old `k8s.gcr.io` images from annotations.
.github/image_licenses.yaml	Replaced Kubernetes CSI image license entries from `k8s.gcr.io` domain to `registry.k8s.io` domain with identical license info.
charts/t8s-cluster/CHANGELOG.md	Added changelog entry for 9.3.0 with new features: RBAC for Teuto staff, audit logging, apiserver resource customization, new pullPolicy template, and a chore for version pinning.
charts/t8s-cluster/README.md	Updated version badge and source URL; extended `controlPlane` schema with optional `resources` property (including `claims`, `limits`, `requests`); added required `remoteGroupID` to `additionalSecurityGroupRules`; formatting improvements.

Suggested reviewers

marvinWolff
tasches

Poem

🐇 A hop to nine point three we bound,
New RBAC rules and logs are found.
Resources flex with claims and more,
Images updated, licenses soar.
Security rules now tightly spun,
Charting progress, work well done! 🎉

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/t8s-cluster/Chart.yaml (1)
18-18: Optional: Update source link to point to the v9.3.0 tag.

The sources entry still references t8s-cluster-v9.2.1. Consider updating it to t8s-cluster-v9.3.0 for consistency:
-  - https://github.com/teutonet/teutonet-helm-charts/tree/t8s-cluster-v9.2.1/charts/t8s-cluster
+  - https://github.com/teutonet/teutonet-helm-charts/tree/t8s-cluster-v9.3.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 dcb28ca and 4901842.

📒 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)

⏰ Context from checks skipped due to timeout of 90000ms (2)

GitHub Check: lint helm chart (t8s-cluster)
GitHub Check: wait-for-checks

🔇 Additional comments (3)

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

1-1: Version bump is correct and consistent.

The charts/t8s-cluster entry was updated from "9.2.1" to "9.3.0" as expected for this release. No other changes to the JSON manifest are needed.

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

3-8: Changelog entry for v9.3.0 looks good.

The new release entry documents the audit logging feature, references issue #1440 and the corresponding commit, and follows the existing formatting conventions.

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

21-21: Chart version updated correctly.

The version field has been bumped from 9.2.1 to 9.3.0, matching the release and manifest changes.

teutonet-bot · 2025-05-05T08:55:54Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

teutonet-bot · 2025-05-15T06:52:26Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

teutonet-bot · 2025-05-15T06:59:01Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

teutonet-bot · 2025-05-16T01:52:40Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

teutonet-bot · 2025-05-19T09:24:08Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

teutonet-bot · 2025-05-20T07:01:40Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

teutonet-bot · 2025-05-28T12:01:14Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

charts/t8s-cluster/ci/hcp-with-resources-values.yaml

charts/t8s-cluster/ci/cp-with-resources-values.yaml

teutonet-bot · 2025-05-29T02:00:05Z

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroupRules-values.yaml

charts/t8s-cluster/ci/hcp-with-resources-values.yaml

charts/t8s-cluster/ci/cp-with-resources-values.yaml