Flux2 v2.9.2, published on July 13, 2026, fixes a Kustomization regression that prevented reconciliation when openapi.path pointed to a URL. The patch also corrects three CRD descriptions that gave operators inaccurate field references.
The full release notes and downloads are on the GitHub release page.
Remote OpenAPI schemas reconcile again ¶
Flux v2.9.1 introduced a regression in kustomize-controller. A Kustomization with openapi.path set to a URL could fail reconciliation with failed to read OpenAPI schema. Flux2 v2.9.2 restores that path.
This is the main operational reason to take the patch. The affected input is explicit and easy to identify during a cluster audit. A data platform may use remote schemas to validate custom resources before Flux applies them. When the schema cannot be read, the affected Kustomization stays outside its intended state even if the manifest and schema URL are otherwise valid.
The release notes do not describe a new flag, field, or schema format. This is a correction to behavior that worked before v2.9.1. Operators affected by the regression should test the same openapi.path URL after the controller update and confirm that the Kustomization returns to successful reconciliation.
CRD descriptions now point at the right fields ¶
Three fixes change CRD descriptions rather than controller behavior. The HelmChart description for .status.url previously pointed readers to BucketStatus.Artifact. It now refers to HelmChartStatus.Artifact, which is the relevant status object.
The ImageRepository description for .status.observedExclusionList also had the wrong location. It referred to spec.lastScanResult instead of status.lastScanResult. That distinction matters when an operator compares the requested image scan configuration with the state observed by image-reflector-controller.
Finally, the ImageUpdateAutomation description for .status.observedSourceRevision contained a stray Go struct declaration. Flux2 v2.9.2 removes that leaked implementation text. None of these three entries is presented as an API shape change. They repair the reference text used when inspecting the installed CRDs and their status fields.
Controller and CLI maintenance stays narrow ¶
The bundle updates the components that contain the fixes. Both kustomize-controller and source-controller move to v1.9.3. image-reflector-controller and image-automation-controller move to v1.2.3. Those versions give operators a precise component inventory when checking a rollout.
The CLI changelog is dependency maintenance. It records two fluxcd/pkg refreshes and a toolkit component update in pull request 5994. The release notes do not claim a new CLI workflow or command surface. Treat this part as packaging work attached to the patch, not as a separate feature.
Upgrade notes ¶
Flux2 v2.9.2 is a stable patch release, not a prerelease. The notes do not announce a breaking API change or a new migration for users already on the current release line.
Operators moving from Flux v2.6 should follow the project’s upgrade procedure for Flux v2.7 and later. For clusters that hit the remote schema regression, record the current Kustomization condition before rollout. After the upgrade, verify that the failed to read OpenAPI schema error clears and that the expected revision reconciles.
The Flux2 v2.9.2 release page remains the source for the component changelog and downloads.
Where to get it ¶
- Release: Flux2 v2.9.2
- Repository: fluxcd/flux2
- Tag:
v2.9.2