Skip to content

Update Flux Operator to 0.20.0 - #934

Merged
Andrei Kvapil (kvaps) merged 1 commit into
cozystack:mainfrom
kingdonb:update-flux-oper
May 15, 2025
Merged

Update Flux Operator to 0.20.0#934
Andrei Kvapil (kvaps) merged 1 commit into
cozystack:mainfrom
kingdonb:update-flux-oper

Conversation

@kingdonb

@kingdonb Kingdon Barrett (kingdonb) commented May 12, 2025

Copy link
Copy Markdown
Member

Now includes a Flux MCP server

(docs: https://fluxcd.control-plane.io/mcp/ - NB: it is not running in the cluster by default, and I haven't tried it yet)

Summary by CodeRabbit

  • Chores
    • Updated Helm chart and app version numbers for Flux Operator and Flux Instance to 0.20.0.
  • Documentation
    • Updated version badges in the README files to reflect the new 0.20.0 release.

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

coderabbitai Bot commented May 12, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The changes update the version and appVersion fields in the Helm chart metadata and corresponding README badges for both the flux-operator and flux-instance packages, incrementing them from 0.19.0 to 0.20.0. No other modifications or functional changes are present.

Changes

Files Change Summary
.../fluxcd-operator/charts/flux-operator/Chart.yaml
.../fluxcd/charts/flux-instance/Chart.yaml
Updated version and appVersion fields from 0.19.0 to 0.20.0
.../fluxcd-operator/charts/flux-operator/README.md
.../fluxcd/charts/flux-instance/README.md
Updated version and appVersion badges from 0.19.0 to 0.20.0

Poem

Hopping along, the versions grow,
From one-nine-oh to two-oh-oh!
Chart and badge in perfect sync,
The numbers rise, the rabbits wink.
With every hop, release anew,
Fresh carrots for the charting crew! 🥕

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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 coderabbitai 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.

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 653e2bc and fd72d7c.

📒 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 (6)
packages/system/fluxcd-operator/charts/flux-operator/Chart.yaml (2)

11-11: AppVersion bump approved
Updating the appVersion to v0.20.0 aligns with the new Flux Operator release.


28-28: Chart version bump approved
Version 0.20.0 correctly reflects the new release and matches appVersion.

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

3-3: Update of version badges approved
Badges for Version and AppVersion have been updated to 0.20.0 and v0.20.0, respectively, matching the Helm chart metadata.

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

3-3: Update of version badges approved
Version and AppVersion badges are now 0.20.0 and v0.20.0, aligning with the corresponding Chart.yaml updates.

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

11-11: AppVersion bump approved
Setting appVersion to v0.20.0 aligns the chart with the new Flux release.


28-28: Chart version bump approved
Version updated to 0.20.0, consistent with the new appVersion.

url: https://github.com/controlplaneio-fluxcd/flux-operator
apiVersion: v2
appVersion: v0.19.0
appVersion: v0.20.0

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.

💡 Verification agent

❓ Verification inconclusive

Verify inclusion of Flux MCP server templates
The PR description mentions adding the Flux MCP server, but I don’t see any new templates or CRDs in this chart. Please confirm that the MCP server manifests are included.


🏁 Script executed:

#!/bin/bash
# Verify that Flux MCP server templates and CRDs are present in the flux-operator chart
rg -R "mcp" -n packages/system/fluxcd-operator/charts/flux-operator/templates

Length of output: 482


Let’s correct the search to run recursively (rg does so by default) and cover the entire chart directory:


🏁 Script executed:

#!/bin/bash
# Search for any MCP-related references across the flux-operator chart
rg -n "mcp" packages/system/fluxcd-operator/charts/flux-operator
# Also check for CustomResourceDefinition CRDs in case they live under crds/
rg -n "CustomResourceDefinition" packages/system/fluxcd-operator/charts/flux-operator/crds

Length of output: 253


Missing Flux MCP server manifests in flux-operator chart
I ran searches across packages/system/fluxcd-operator/charts/flux-operator and found:

  • No references to “mcp” in any files
  • No crds/ directory or CRD definitions under templates/

Please add the Flux MCP server templates and corresponding CRDs (e.g. under a new crds/ folder and in templates/) so that the MCP server is actually included in this chart.

@kvaps Andrei Kvapil (kvaps) left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM, thanks

@kvaps
Andrei Kvapil (kvaps) merged commit de1b38c into cozystack:main May 15, 2025
Timofei Larkin (lllamnyp) pushed a commit that referenced this pull request May 20, 2025
Now includes a Flux MCP server

(docs: https://fluxcd.control-plane.io/mcp/ - NB: it is not running in
the cluster by default, and I haven't tried it yet)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Chores**
- Updated Helm chart and app version numbers for Flux Operator and Flux
Instance to 0.20.0.
- **Documentation**
- Updated version badges in the README files to reflect the new 0.20.0
release.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

(cherry picked from commit de1b38c)
Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>
IvanHunters added a commit that referenced this pull request Jul 2, 2026
…issue)

Reviewer nit was to file an upstream issue so the workaround does
not silently outlive its cause. Checked first — fluxcd/pkg already
has one open: #934 \"patch.Helper creates race conditions in
downstream controllers\" (May 2025). Same root cause we traced:
patch.Helper writes .status and .status.conditions as separate
apiserver requests, so an etcd blip between the two leaves the
object half-persisted. The upstream issue is broader than just
source-watcher — every fluxcd downstream controller consuming
fluxcd/pkg's runtime patch helper is affected.

Update the TODO(remove) marker on our workaround to point at
that issue and note that both source-watcher v2.1.0 and v2.2.x
(flux-aio latest) pull the same fluxcd/pkg runtime, so bumping
source-watcher alone does not remove the need for this synthesis.
Compile + unit tests unchanged.

Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
IvanHunters added a commit that referenced this pull request Jul 4, 2026
…issue)

Reviewer nit was to file an upstream issue so the workaround does
not silently outlive its cause. Checked first — fluxcd/pkg already
has one open: #934 \"patch.Helper creates race conditions in
downstream controllers\" (May 2025). Same root cause we traced:
patch.Helper writes .status and .status.conditions as separate
apiserver requests, so an etcd blip between the two leaves the
object half-persisted. The upstream issue is broader than just
source-watcher — every fluxcd downstream controller consuming
fluxcd/pkg's runtime patch helper is affected.

Update the TODO(remove) marker on our workaround to point at
that issue and note that both source-watcher v2.1.0 and v2.2.x
(flux-aio latest) pull the same fluxcd/pkg runtime, so bumping
source-watcher alone does not remove the need for this synthesis.
Compile + unit tests unchanged.

Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
IvanHunters added a commit that referenced this pull request Jul 4, 2026
…issue)

Reviewer nit was to file an upstream issue so the workaround does
not silently outlive its cause. Checked first — fluxcd/pkg already
has one open: #934 \"patch.Helper creates race conditions in
downstream controllers\" (May 2025). Same root cause we traced:
patch.Helper writes .status and .status.conditions as separate
apiserver requests, so an etcd blip between the two leaves the
object half-persisted. The upstream issue is broader than just
source-watcher — every fluxcd downstream controller consuming
fluxcd/pkg's runtime patch helper is affected.

Update the TODO(remove) marker on our workaround to point at
that issue and note that both source-watcher v2.1.0 and v2.2.x
(flux-aio latest) pull the same fluxcd/pkg runtime, so bumping
source-watcher alone does not remove the need for this synthesis.
Compile + unit tests unchanged.

Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
IvanHunters added a commit that referenced this pull request Jul 5, 2026
…issue)

Reviewer nit was to file an upstream issue so the workaround does
not silently outlive its cause. Checked first — fluxcd/pkg already
has one open: #934 \"patch.Helper creates race conditions in
downstream controllers\" (May 2025). Same root cause we traced:
patch.Helper writes .status and .status.conditions as separate
apiserver requests, so an etcd blip between the two leaves the
object half-persisted. The upstream issue is broader than just
source-watcher — every fluxcd downstream controller consuming
fluxcd/pkg's runtime patch helper is affected.

Update the TODO(remove) marker on our workaround to point at
that issue and note that both source-watcher v2.1.0 and v2.2.x
(flux-aio latest) pull the same fluxcd/pkg runtime, so bumping
source-watcher alone does not remove the need for this synthesis.
Compile + unit tests unchanged.

Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
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