Skip to content

chore(deps): update fluxcd/flux2 action to v2.8.8#42

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/fluxcd-flux2-2.x
Open

chore(deps): update fluxcd/flux2 action to v2.8.8#42
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/fluxcd-flux2-2.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 24, 2026

This PR contains the following updates:

Package Type Update Change
fluxcd/flux2 action minor v2.7.5v2.8.8

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.8.8

Compare Source

v2.8.7

Compare Source

Highlights

Flux v2.8.7 is a patch release that includes a bug fix in kustomize-controller, a CVE fix in source-controller and image-automation-controller via go-git v5.19.0, and dependency updates. 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 management of objects annotated with kustomize.toolkit.fluxcd.io/ssa: IfNotPresent where non-namespaced resources were being deleted and recreated on each reconciliation (kustomize-controller)

Improvements:

  • Update go-git to v5.19.0 which fixes CVE-2026-45022 (source-controller, image-automation-controller)
  • Update fluxcd/pkg dependencies (source-controller, kustomize-controller, image-automation-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.6...v2.8.7

v2.8.6

Compare Source

Highlights

Flux v2.8.6 is a patch release that includes bug fixes and improvements across helm-controller, image-automation-controller, kustomize-controller, notification-controller, and source-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 a post-renderer conflict between overlapping hooks and templates (helm-controller)
  • Ignore force replace when server-side apply is enabled (helm-controller)
  • Fix a regression where generic providers would not forward commit status events (notification-controller)
  • Require the audience field on the GCR Receiver secret for tighter verification — will become mandatory in Flux v2.9 (notification-controller)

Improvements:

  • Introduce the MigrateAPIVersion feature gate for migrating the API version of resources in managed field entries (kustomize-controller)
  • Update go-git to v5.18.0 bringing performance improvements for Git operations (source-controller, image-automation-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.5...v2.8.6

v2.8.5

Compare Source

Highlights

Flux v2.8.5 is a patch release that includes bug fixes and improvements across kustomize-controller, source-controller, and notification-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 a race condition where a cancelled reconciliation could leave stale data in the cache, causing Kustomizations to get stuck (kustomize-controller)
  • Fix Azure Blob prefix option not being passed to the storage client (source-controller)

Improvements:

  • Improve error message for encrypted SSH keys without password (source-controller)
  • Add optional email and audience fields to the GCR Receiver for tighter verification (notification-controller)
  • Add provider manifest example for Azure Event Hub managed identity authentication (notification-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.4...v2.8.5

v2.8.4

Compare Source

Highlights

Flux v2.8.4 is a patch release that includes fixes for the Flux CLI. 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 flux build ks and flux diff ks on Windows
  • Fix --source flag validation in create kustomization command

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.3...v2.8.4

v2.8.3

Compare Source

Highlights

Flux v2.8.3 is a patch release that fixes a regression in 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 templating errors for charts that include --- in the content, e.g. YAML separators, embedded scripts, CAs inside ConfigMaps (helm-controller)

Components changelog

CLI changelog

Full Changelog: fluxcd/flux2@v2.8.2...v2.8.3

v2.8.2

Compare Source

Highlights

Flux v2.8.2 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 enqueuing new reconciliation requests for events on source Flux objects when they are already reconciling the revision present in the watch event (kustomize-controller, helm-controller)
  • Fix the Go templates bug of YAML separator --- getting concatenated to apiVersion: by updating to Helm 4.1.3 (helm-controller)
  • Fix canceled HelmReleases getting stuck when they don't have a retry strategy configured by introducing a new feature gate DefaultToRetryOnFailure that improves the experience when the CancelHealthCheckOnNewRevision is enabled (helm-controller)
  • Fix the auth scope for Azure Container Registry to use the ACR-specific scope (source-controller, image-reflector-controller)
  • Fix potential Denial of Service (DoS) during TLS handshakes (CVE-2026-27138) by building all controllers with Go 1.26.1

Components changelog

CLI changelog

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

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


Configuration

📅 Schedule: (UTC)

  • 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 changed the title chore(deps): update fluxcd/flux2 action to v2.8.0 chore(deps): update fluxcd/flux2 action to v2.8.1 Feb 27, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 688a330 to 4cd850e Compare February 27, 2026 12:37
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Feb 27, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 4cd850e to cb2f974 Compare March 5, 2026 10:58
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.1 chore(deps): update fluxcd/flux2 action to v2.8.2 Mar 12, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from cb2f974 to f17b304 Compare March 12, 2026 18:54
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.2 chore(deps): update fluxcd/flux2 action to v2.8.3 Mar 16, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from f17b304 to 8b6f52b Compare March 16, 2026 14:05
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 8b6f52b to 4325798 Compare March 26, 2026 17:50
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.3 chore(deps): update fluxcd/flux2 action to v2.8.4 Apr 7, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 4325798 to b9802a1 Compare April 7, 2026 16:32
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.4 chore(deps): update fluxcd/flux2 action to v2.8.5 Apr 7, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from b9802a1 to f178a60 Compare April 7, 2026 20:54
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from f178a60 to 1ae4198 Compare April 15, 2026 09:57
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.5 chore(deps): update fluxcd/flux2 action to v2.8.6 Apr 21, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 1ae4198 to 0b0254c Compare April 21, 2026 12:32
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 0b0254c to 83af995 Compare April 29, 2026 10:10
@renovate renovate Bot requested a review from a team as a code owner April 29, 2026 10:10
@renovate renovate Bot requested a review from mksinghtx April 29, 2026 10:10
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.6 chore(deps): update fluxcd/flux2 action to v2.8.7 May 12, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 83af995 to c458217 Compare May 12, 2026 14:42
@renovate renovate Bot changed the title chore(deps): update fluxcd/flux2 action to v2.8.7 chore(deps): update fluxcd/flux2 action to v2.8.8 May 20, 2026
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from c458217 to 40b8f79 Compare May 20, 2026 14:15
@renovate renovate Bot force-pushed the renovate/fluxcd-flux2-2.x branch from 40b8f79 to 52f50b8 Compare May 20, 2026 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant