Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 30, 2025

This PR contains the following updates:

Package Update Change
flux minor 2.6.4 -> 2.7.3
flux minor 2.16.4 -> 2.17.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

fluxcd/flux2 (flux)

v2.7.3

Compare Source

v2.7.2

Compare Source

Highlights

Flux v2.7.2 is a patch release that comes with security fixes. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

All Flux components are now built with Go 1.25.2 which includes fixes for vulnerabilities in the Go stdlib that could lead to denial of service. The list of security fixes can be found in the Go 1.25.2 release notes.

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.7.1...v2.7.2

v2.7.1

Compare Source

Highlights

Flux v2.7.1 is a patch release that comes with various improvements and fixes. Users are encouraged to upgrade for the best experience.

ℹ️ Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from Flux v2.6 to the latest version.

Improvements:

  • Extend flux migrate with support for migrating manifests in Git repositories to the latest API versions.
  • Add recommendations for configuring HelmReleases on production environments.

Fixes:

  • Fix flux migrate command to handle managed fields properly.
  • Fix self-signed TLS cert handling for public Helm repositories in source-controller.
  • Fix the default API versions used by receivers in notification-controller.
  • Fix redundant Ready condition patching in helm-controller.
  • Fix workload identity configuration examples for kubeconfig in helm-controller and kustomize-controller.

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.7.0...v2.7.1

v2.7.0

Compare Source

Highlights

Flux v2.7.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a compressive overview of new features and API changes included in this release, please refer to the Announcing Flux 2.7 GA blog post.

Overview of the new features:

  • General availability release of the Image Automation APIs (ImagePolicy, ImageRepository, ImageUpdateAutomation)
  • Watch for changes in ConfigMaps and Secrets references (Kustomization, HelmRelease)
  • Support for remote cluster authentication using Workload Identity (Kustomization, HelmRelease)
  • Extend the readiness evaluation of dependencies with CEL expressions (Kustomization, HelmRelease)
  • Support for global SOPS Age decryption keys on single-tenant clusters (Kustomization)
  • Support for optional Kustomize components (Kustomization)
  • Introduce RetryOnFailure lifecycle management strategy (HelmRelease)
  • Support mTLS for sending alerts to external systems (Provider)
  • Object-level workload identity authentication (Bucket, Provider)
  • Support mTLS for GitHub App transport (GitRepository, ImageUpdateAutomation, Provider)
  • OpenTelemetry tracing for Kustomization and HelmRelease reconciliation (Provider)
  • Support for 3rd-party source controllers (ExternalArtifact)
  • Support for source composition and decomposition patterns (ArtifactGenerator)
  • CancelHealthCheckOnNewRevision feature gate (kustomize-controller)
  • GitSparseCheckout feature gate (image-automation-controller)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.32 >= 1.32.0
v1.33 >= 1.33.0
v1.34 >= 1.34.1

[!NOTE]
Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using Flux Operator. The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts, and S3-compatible storage.

Upgrade procedure

⚠️ The Flux APIs v1beta1 and v2beta1 (deprecated in 2023) have reached end-of-life and have been removed from the CRDs.

Unless you are using Flux Operator to deploy the Flux controllers, you must run the flux migrate command on clusters before upgrading.

For more details, please refer to the Flux v2.7 upgrade guide.

Components changelog

New Documentation

CLI changelog

New Contributors

Full Changelog: fluxcd/flux2@v2.6.0...v2.7.0

fluxcd-community/helm-charts (flux)

v2.17.0

Compare Source

A Helm chart for flux2


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency flux to v2.7.0 chore(deps): update dependency flux to v2.7.1 Oct 6, 2025
@renovate renovate bot force-pushed the renovate/flux-2.x branch 2 times, most recently from 4f44fc3 to 655c1f3 Compare October 8, 2025 21:35
@renovate renovate bot changed the title chore(deps): update dependency flux to v2.7.1 chore(deps): update dependency flux to v2.7.2 Oct 8, 2025
@renovate renovate bot force-pushed the renovate/flux-2.x branch from 655c1f3 to 497475b Compare October 9, 2025 11:12
@renovate renovate bot changed the title chore(deps): update dependency flux to v2.7.2 chore(deps): update dependency flux Oct 9, 2025
@renovate renovate bot force-pushed the renovate/flux-2.x branch 4 times, most recently from 95e549d to cdaa0dc Compare October 29, 2025 13:37
@renovate renovate bot force-pushed the renovate/flux-2.x branch from cdaa0dc to 36cfd20 Compare October 29, 2025 14:06
@renovate renovate bot force-pushed the renovate/flux-2.x branch from 36cfd20 to f5eaea0 Compare October 29, 2025 23:21
@renovate renovate bot force-pushed the renovate/flux-2.x branch 2 times, most recently from fce214b to f073db2 Compare October 30, 2025 01:36
@renovate renovate bot force-pushed the renovate/flux-2.x branch from f073db2 to 9257923 Compare October 30, 2025 01:54
Signed-off-by: Ryan VanGundy <85766511+rmvangun@users.noreply.github.com>
@renovate
Copy link
Contributor Author

renovate bot commented Oct 30, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@rmvangun rmvangun merged commit a164309 into main Oct 30, 2025
7 checks passed
@rmvangun rmvangun deleted the renovate/flux-2.x branch October 30, 2025 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants