Skip to content

Update Flux Operator (v0.24.1) - #1207

Merged
Andrei Kvapil (kvaps) merged 2 commits into
cozystack:mainfrom
kingdonb:update-flux-operator
Jul 16, 2025
Merged

Update Flux Operator (v0.24.1)#1207
Andrei Kvapil (kvaps) merged 2 commits into
cozystack:mainfrom
kingdonb:update-flux-operator

Conversation

@kingdonb

@kingdonb Kingdon Barrett (kingdonb) commented Jul 16, 2025

Copy link
Copy Markdown
Member

Comes with Flux v2.6.4 manifests included, other release notes:

https://github.com/controlplaneio-fluxcd/flux-operator/releases/tag/v0.24.1

Summary by CodeRabbit

  • Chores
    • Updated Helm chart versions and app versions for Flux Operator and Flux Instance from 0.24.0 to 0.24.1.
    • Refreshed version badges in related documentation to reflect the new release.

Signed-off-by: Kingdon B <kingdon@urmanac.com>
Signed-off-by: Kingdon B <kingdon@urmanac.com>
@coderabbitai

coderabbitai Bot commented Jul 16, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

This update increments the version and appVersion fields from 0.24.0 to 0.24.1 in the Helm chart metadata and README badges for both the flux-operator and flux-instance packages. No functional or configuration changes were introduced.

Changes

Files Change Summary
.../charts/flux-operator/Chart.yaml
.../charts/flux-instance/Chart.yaml
Bumped chart version and appVersion to 0.24.1
.../charts/flux-operator/README.md
.../charts/flux-instance/README.md
Updated version badges to 0.24.1

Possibly related PRs

Suggested labels

documentation, size:XS

Suggested reviewers

  • lllamnyp
  • klinch0
  • kvaps

Poem

A gentle hop, a version nudge,
0.24.1—no need to judge!
Badges shine with numbers new,
No code disturbed, just passing through.
🐇✨
Charts and docs aligned in sync,
A tiny change—blink and wink!


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7a74936 and 2466a0a.

📒 Files selected for processing (4)
  • packages/system/fluxcd-operator/charts/flux-operator/Chart.yaml (2 hunks)
  • packages/system/fluxcd-operator/charts/flux-operator/README.md (1 hunks)
  • packages/system/fluxcd/charts/flux-instance/Chart.yaml (2 hunks)
  • packages/system/fluxcd/charts/flux-instance/README.md (1 hunks)
🔇 Additional comments (4)
packages/system/fluxcd-operator/charts/flux-operator/README.md (1)

3-3: Version badge bump looks consistent

Chart and appVersion badges correctly moved to 0.24.1; nothing else changed.

packages/system/fluxcd/charts/flux-instance/README.md (1)

3-3: README badge updated correctly

The flux-instance README now reflects 0.24.1, matching the chart metadata.

packages/system/fluxcd-operator/charts/flux-operator/Chart.yaml (1)

11-11: Chart version ↗ 0.24.1 — double-check release pipeline

Both appVersion and version are bumped. Ensure:

  1. A corresponding Git tag/container image v0.24.1 exists or will be produced.
  2. Any Chart.lock or provenance files (if used) are regenerated.

No other content change detected.

Also applies to: 28-28

packages/system/fluxcd/charts/flux-instance/Chart.yaml (1)

11-11: Aligned version increment to 0.24.1

Change is straightforward and mirrors the operator chart. Same release-artifact checks apply.

Also applies to: 28-28


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.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello Kingdon Barrett (@kingdonb), I'm Gemini Code Assist1! 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 updates the Helm charts for the Flux Operator and its associated Flux Instance to align with the release of Flux Operator v0.24.1. This update ensures that the chart metadata and documentation accurately reflect the latest supported version of the operator, which also bundles updated Flux manifests.

Highlights

  • Flux Operator Version Update: Updated the appVersion and chart version fields in the Chart.yaml files for both the flux-operator and flux-instance Helm charts from 0.24.0 to 0.24.1.
  • Documentation Synchronization: Synchronized the version badges in the README.md files for both the flux-operator and flux-instance Helm charts to reflect the new 0.24.1 version.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 (@gemini-code-assist) Responds in comments when explicitly tagged, both in issue 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 is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on Gemini (@gemini-code-assist) comments to provide feedback.

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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the Flux Operator to version v0.24.1. The changes correctly bump the version and appVersion in the Chart.yaml files for the flux-operator and flux-instance charts, and update the corresponding README.md files.

The version updates are consistent across all modified files. After a thorough review of the changes, I have not identified any issues of medium or higher severity. The pull request correctly implements the intended version update.

@kvaps
Andrei Kvapil (kvaps) merged commit 096227d into cozystack:main Jul 16, 2025
9 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants