Skip to content

chore(deps): update fluxcd/flux2 to 2.8.1#84

Open
zon-renovate wants to merge 1 commit intomainfrom
renovate/fluxcd-flux2-2.x
Open

chore(deps): update fluxcd/flux2 to 2.8.1#84
zon-renovate wants to merge 1 commit intomainfrom
renovate/fluxcd-flux2-2.x

Conversation

@zon-renovate
Copy link
Collaborator

@zon-renovate zon-renovate commented Jun 21, 2025

This PR contains the following updates:

Package Update Change
fluxcd/flux2 minor 2.6.12.8.1

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.8.1

Compare Source

Highlights

Flux v2.8.1 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:

  • Fix Git commit status events being dropped for Kustomizations (notification-controller)
  • Fix health check for StatefulSets when the Pods are Pending/Unschedulable during rollout (helm-controller, kustomize-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.0...v2.8.1

v2.8.0

Compare Source

Highlights

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

Overview of the new features:

  • Helm v4 support, including server-side apply and kstatus-based health checking (HelmRelease)
  • Readiness evaluation of Helm-managed objects with CEL expressions (HelmRelease)
  • Improved observability of Helm releases with inventory tracking in .status.inventory (HelmRelease)
  • Reduced the mean time to recovery of Flux-managed applications via CancelHealthCheckOnNewRevision feature gate (Kustomization, HelmRelease)
  • Support for commenting on Pull Requests directly from Flux notifications (Provider)
  • Custom SSA apply stages for ordering resource application in kustomize-controller (Kustomization)
  • Automatic GitHub App installation ID lookup from the repository owner (GitRepository, ImageUpdateAutomation, Provider)
  • Support for Cosign v3 for verifying OCI artifacts and container images (OCIRepository)
  • ArtifactGenerator support for extracting and modifying Helm charts (ArtifactGenerator)
  • Bypass cache when fetching source objects via DirectSourceFetch feature gate (Kustomization, HelmRelease, ArtifactGenerator)

❤️ 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.33 >= 1.32.0
v1.34 >= 1.34.1
v1.35 >= 1.35.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

⚠️ The Flux APIs v1beta2 and v2beta2 (deprecated in 2024) have reached end-of-life and have been removed from the CRDs.

Please follow the Upgrade Procedure for Flux v2.7+ for a smooth upgrade from older versions of Flux to v2.8.

Components changelog

CLI changelog

New Contributors

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

v2.7.5

Compare Source

Highlights

Flux v2.7.5 is a patch release that comes with fixes to helm-controller. 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:

  • Fix HelmRelease history truncation when using the RetryOnFailure strategy.

⚠️ Note that signature verification for OCI artifacts in source-controller is not compatible with Cosign v3.
Flux 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.4...v2.7.5

v2.7.4

Compare Source

Highlights

Flux v2.7.4 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:

  • Add DisableConfigWatchers feature gate to all controllers for disabling the Secrets/ConfigMaps watchers
  • Fix Workload Identity for Azure China Cloud in all controllers
  • Update Helm Go SDK to v3.19.2 fixing schema validation issues in helm-controller
  • Skip secret decryption for remote kustomize patches in kustomize-controller
  • Improve post-build error reporting in kustomize-controller
  • Add ArtifactGenerator to aggregated RBAC roles

⚠️ Note that signature verification for OCI artifacts in source-controller is not compatible with Cosign v3.
Flux 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.3...v2.7.4

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


Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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 has been generated by Renovate Bot.

@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.6.2 chore(deps): update dependency fluxcd/flux2 to v2.6.3 Jun 27, 2025
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from b2b42f6 to 67a418a Compare June 27, 2025 12:10
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 67a418a to 4e8bb82 Compare July 8, 2025 10:11
@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.6.3 chore(deps): update dependency fluxcd/flux2 to v2.6.4 Jul 8, 2025
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 4e8bb82 to f151f91 Compare September 30, 2025 08:44
@zon-renovate zon-renovate 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
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from f151f91 to 3146081 Compare October 6, 2025 17:12
@zon-renovate zon-renovate 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
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 3146081 to 984260b Compare October 8, 2025 19:12
@zon-renovate zon-renovate 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
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch 2 times, most recently from f5fd07f to d5032bc Compare October 17, 2025 07:12
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from d5032bc to 019ac2b Compare October 28, 2025 17:12
@zon-renovate zon-renovate 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
@zon-renovate zon-renovate 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
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 019ac2b to f202e2a Compare November 24, 2025 16:13
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from f202e2a to 002e259 Compare November 27, 2025 12:11
@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.7.4 chore(deps): update dependency fluxcd/flux2 to v2.7.5 Nov 27, 2025
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 002e259 to 617fb78 Compare January 30, 2026 15:13
@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.7.5 chore(deps): update dependency fluxcd/flux2 to v2.8.0 Feb 24, 2026
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 617fb78 to 1071a32 Compare February 24, 2026 14:14
@zon-renovate zon-renovate force-pushed the renovate/fluxcd-flux2-2.x branch from 1071a32 to 3fc3b8b Compare February 27, 2026 12:43
@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.8.0 chore(deps): update dependency fluxcd/flux2 to v2.8.1 Feb 27, 2026
@zon-renovate zon-renovate changed the title chore(deps): update dependency fluxcd/flux2 to v2.8.1 chore(deps): update fluxcd/flux2 to 2.8.1 Mar 3, 2026
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.

1 participant