Skip to content

chore(deps): update dependency fluxcd/flux2 to v2.7.4 #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency fluxcd/flux2 to v2.7.4 #13

wants to merge 1 commit into from
+3,015 −5,404

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 28, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
fluxcd/flux2 minor v2.5.1 -> v2.7.4

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.7.4

Compare Source

v2.7.3

Compare Source

Highlights

Flux v2.7.3 is a patch release that comes with various 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.

Fixes:

  • Restore SOCKS5 proxy support in all controllers
  • Fix status reporting of HelmReleases with RetryOnFailure strategy
  • Automated retries for ImagePolicies when no image tags are found in the database
  • Fix alerting for Telegram's message_thread_id
  • Allow running kustomize-controller and helm-controller on the same loopback interface as source-watcher

⚠️ Note that signature verification for OCI artifacts in source-controller is not compatible with Cosign v3. Users are advised to use Cosign v2.6 for signing Flux OCI artifacts and Helm charts, until support for Cosign v3 is added in Flux v2.8.

Components changelog

CLI changelog

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

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

v2.6.4

Compare Source

Highlights

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

Fixes:

  • Fix for SOPS decryption with US Government KMS keys failing with the error:
STS: AssumeRoleWithWebIdentity, https response error\n   StatusCode: 0, RequestID: ,
request send failed, Post\n \"https://sts.arn.amazonaws.com/\": dial tcp:
lookupts.arn.amazonaws.com on 10.100.0.10:53: no such host

Components changelog

CLI changed

Full Changelog: fluxcd/flux2@v2.6.3...v2.6.4

v2.6.3

Compare Source

Highlights

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

Fixes:

  • Fix for rsa-sha2-512 and rsa-sha2-256 algorithms not being prioritized for ssh-rsa host keys in source-controller, image-automation-controller and Flux CLI bootstrap.

Components changelog

CLI changed

Full Changelog: fluxcd/flux2@v2.6.2...v2.6.3

v2.6.2

Compare Source

Highlights

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

Fixes:

  • Fix authentication for flux push artifact --provider=azure on Azure DevOps runners.
  • Fix OIDC authentication for Amazon ECR Public in source-controller and image-reflector-controller.
  • Fix knownhosts key mismatch regression bug in the Flux CLI, source-controller and image-automation-controller.

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.6.1...v2.6.2

v2.6.1

Compare Source

Highlights

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

Fixes:

  • Fix a bug introduced in image-reflector-controller v0.35.0 that was causing spurious error events for policies during image repository reconciliation.
  • Fix excessive logging in image-reflector-controller after a restart when the image tags cache is empty.

Components changelog

  • image-reflector-controller v0.35.1

CLI changelog

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

v2.6.0

Compare Source

Highlights

Flux v2.6.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.6 GA blog post.

Overview of the new features:

  • General availability release for the Flux OCI Artifacts APIs and flux artifact commands
  • Support for OCI digests pinning (ImagePolicy, ImageUpdateAutomation)
  • Object-level workload identity authentication (OCIRepository, ImageRepository, Kustomization, Alert Provider)
  • Cache registry credentials for cloud providers (OCIRepository, ImageRepository)
  • Git HTTP/S Mutual TLS authentication (GitRepository, ImageUpdateAutomation)
  • Support for sparse checkout (GitRepository)
  • Support for GitHub App authentication (Alert Provider)
  • Support for managed Identity authentication to Azure Event Hub (Alert Provider)
  • Customize the ID of the Git commit status with CEL expressions (Alert Provider)
  • WaitForTermination deletion policy (Kustomization)
  • DisableChartDigestTracking feature gate (HelmRelease)

❤️ 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.31 >= 1.31.0
v1.32 >= 1.32.0
v1.33 >= 1.33.0

[!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

Upgrade Flux from v2.5.0 to v2.6.0 by following the upgrade guide.

To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:

  1. Set apiVersion: source.toolkit.fluxcd.io/v1 in the YAML files that contain OCIRepository definitions.
  2. Add an annotation api.fluxcd.io/upgrade: "v2.6.0" to the OCIRepository resources. (this is not required if Flux Operator is used for upgrade)
  3. Commit, push, and reconcile the API version changes.

Bumping the APIs version in manifests can be done gradually.
It is advised to not delay this procedure as the deprecated versions will be removed after 6 months.

Components changelog

New Documentation

What's Changed

New Contributors

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

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • 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 force-pushed the renovate/fluxcd-flux2-2.x branch 19 times, most recently from 21112b3 to 30bba4d Compare September 30, 2025 10:59
@renovate renovate bot changed the title chore(deps): update dependency fluxcd/flux2 to v2.6.4 chore(deps): update dependency fluxcd/flux2 to v2.7.0 Sep 30, 2025
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-2.x branch 10 times, most recently from 2f4eaa8 to 52e13fe Compare October 5, 2025 17:06
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-2.x branch 7 times, most recently from 9fd8b33 to 775bd32 Compare October 6, 2025 06:32
@renovate renovate bot changed the title chore(deps): update dependency fluxcd/flux2 to v2.7.0 chore(deps): update dependency fluxcd/flux2 to v2.7.1 Oct 6, 2025
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-2.x branch 4 times, most recently from 214409f to 4c2c1e7 Compare October 8, 2025 21:04
@renovate renovate bot changed the title chore(deps): update dependency fluxcd/flux2 to v2.7.1 chore(deps): update dependency fluxcd/flux2 to v2.7.2 Oct 8, 2025
@renovate renovate bot changed the title chore(deps): update dependency fluxcd/flux2 to v2.7.2 chore(deps): update dependency fluxcd/flux2 to v2.7.3 Oct 28, 2025
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-2.x branch from 4c2c1e7 to 5816554 Compare October 28, 2025 20:37
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-2.x branch from 5816554 to aa4f3fb Compare November 13, 2025 10:21
@renovate renovate bot changed the title chore(deps): update dependency fluxcd/flux2 to v2.7.3 chore(deps): update dependency fluxcd/flux2 to v2.7.4 Nov 24, 2025
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-2.x branch from aa4f3fb to 4788ab6 Compare November 24, 2025 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant