# Flux v2.7.5

2025-11-27 · [Original release notes](https://github.com/fluxcd/flux2/releases/tag/v2.7.5) · [Full summary](https://ratatosk.io/en/releases/flux/v2.7.5)

Breaking changes 4 · Important fixes 2 · Enhancements 4

## Check before upgrading

### Known issues

- **source-controller OCI signature verification does not support Cosign v3**: The note recommends Cosign v2.6 for signing Flux OCI artifacts and Helm charts until Flux v2.8 adds Cosign v3 support.
  > :warning: 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](https://fluxcd.io/flux/flux-gh-action/#push-and-sign-kubernetes-manifests-to-container-registries) for signing Flux OCI artifacts and Helm charts, until support for Cosign v3 is added in Flux v2.8.

### Upgrade guide

- **Flux v2.7+ upgrade procedure for phasing out deprecated beta APIs**
  > ℹ️ Please follow the [Upgrade Procedure for Flux v2.7+](https://github.com/fluxcd/flux2/discussions/5572) for a smooth upgrade from Flux v2.6 to the latest version.

  - Upgrade guide from Flux v2.6 to the latest version
  - Manual cluster migration with the Flux CLI
  - Guide to automated cluster migration with Flux Operator
  - Flux v2.9 removes the `image.toolkit.fluxcd.io/v1beta2` and `notification.toolkit.fluxcd.io/v1beta2` APIs: Both APIs were deprecated in 2024 and reach end of life in Q2 2026.
  - Flux CLI upgrade instructions
  - Flux resources migrated to v2.6 stable APIs: The migration uses `flux migrate -v 2.6 -f .` across the repository, followed by committing and pushing the changes.
  - Guide to migrating Flux custom resources to their latest API version
  - Image update automation definition migration: The note recommends migrating them to the latest stable versions with `flux migrate -v 2.8 -f .`, then committing and pushing the changes.
  - Flux v2.6 stable API migration instructions

## Breaking changes (4)

### Flux removes five deprecated beta API versions

- Affects: manifests, stored resources, or clients using `source.toolkit.fluxcd.io/v1beta1`, `kustomize.toolkit.fluxcd.io/v1beta1`, `helm.toolkit.fluxcd.io/v2beta1`, `image.toolkit.fluxcd.io/v1beta1`, or `notification.toolkit.fluxcd.io/v1beta1` (Inferred)

These API versions were deprecated in 2023; the note does not say whether Flux still served or accepted them in the immediately previous release.

> In Flux v2.7, the following deprecated API versions have been removed:
> - `source.toolkit.fluxcd.io/v1beta1`
> - `kustomize.toolkit.fluxcd.io/v1beta1`
> - `helm.toolkit.fluxcd.io/v2beta1`
> - `image.toolkit.fluxcd.io/v1beta1`
> - `notification.toolkit.fluxcd.io/v1beta1`
> > The beta1 API were deprecated in 2023 and have reached their end-of-life.

https://github.com/fluxcd/flux2/discussions/5572

### Alert `spec.summary` removed in Flux v2.10

- Affects: Alert resources using `spec.summary` (Inferred)

The note names `spec.eventMetadata.summary` in `notification.toolkit.fluxcd.io/v1` as the replacement.

> - Alert `spec.summary` (replaced by `spec.eventMetadata.summary` in `notification.toolkit.fluxcd.io/v1`)

https://github.com/fluxcd/flux2/discussions/5572

### Provider `spec.proxy` removed

- Affects: Flux setups with Provider resources that use `spec.proxy`. (Inferred)

> - Provider `spec.proxy` (replaced by `spec.proxySecretRef` in `notification.toolkit.fluxcd.io/v1`)

https://github.com/fluxcd/flux2/discussions/5572

### Provider `spec.interval` removed

- Affects: Provider resources that specify `spec.interval` (Inferred)
- Action required: Use Flux CLI v2.9.0 or later; migrate Git resources to the Flux v2.6 stable APIs and reconcile them; migrate Flux custom resources in Kubernetes etcd; then upgrade Flux components to v2.9.

The note says the field was unused.

> - Provider `spec.interval` (unused)

https://github.com/fluxcd/flux2/discussions/5572

## Important fixes (2)

### HelmRelease history truncation fixed

- Affects: HelmReleases using the `RetryOnFailure` strategy

Before this release, HelmRelease history was truncated.

> - Fix HelmRelease history truncation when using the `RetryOnFailure` strategy.

### HelmRelease retry history truncation fixed

- Affects: HelmRelease resources using the `RetryOnFailure` strategy

When retry handling was active, `.status.history` could fill up etcd. During an active retry, history is now truncated to the five most recent snapshots, ordered by descending version.

> - helm-controller [v1.4.5](https://github.com/fluxcd/helm-controller/blob/v1.4.5/CHANGELOG.md)
> Fixes:
> - Fix HelmRelease history truncation when using the `RetryOnFailure` strategy.
> Fixes:
> - Fix history truncation logic for RetryOnFailure
>   [#1360](https://github.com/fluxcd/helm-controller/pull/1360)

## Enhancements (4)

- Flux CLI Helm-controller dependency and manifests updated to `v1.4.5`
- New `source-watcher` component (To use: `--components-extra=source-watcher` flag)
- Flux Operator upgrades FluxInstance to Flux 2.9 (To use: Set `spec.distribution.version` to `2.9.x`; enabling `source-watcher` is optional.)
- Optional `source-watcher` component enablement (To use: Flux 2.9 and `source-watcher` in the `FluxInstance` `components` list)

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
