Update Flux Operator to 0.20.0 - #934
Conversation
Signed-off-by: Kingdon B <kingdon@urmanac.com>
WalkthroughThe 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
Poem
Tip ⚡️ Faster reviews with caching
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 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 theappVersiontov0.20.0aligns with the new Flux Operator release.
28-28: Chart version bump approved
Version0.20.0correctly reflects the new release and matchesappVersion.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 to0.20.0andv0.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 now0.20.0andv0.20.0, aligning with the corresponding Chart.yaml updates.packages/system/fluxcd/charts/flux-instance/Chart.yaml (2)
11-11: AppVersion bump approved
SettingappVersiontov0.20.0aligns the chart with the new Flux release.
28-28: Chart version bump approved
Version updated to0.20.0, consistent with the newappVersion.
| url: https://github.com/controlplaneio-fluxcd/flux-operator | ||
| apiVersion: v2 | ||
| appVersion: v0.19.0 | ||
| appVersion: v0.20.0 |
There was a problem hiding this comment.
💡 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/templatesLength 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/crdsLength 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 undertemplates/
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.
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>
…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>
…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>
…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>
…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>
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