Flux Roadmap

Milestones

The Flux project roadmap is divided into milestones representing minor releases, each with a set of goals and tasks. The milestones marked as provisional are subject to change based on the project’s priorities and the community’s feedback.

Please note that the Flux maintainers prioritize fixes to defects affecting GA APIs and security issues over new features. Depending on the volume of incoming issues and the complexity of the fixes, the roadmap may be adjusted and new features may be postponed to the next milestone.

v2.8 (Q1 2026)

Status: In Progress

The primary goal of this milestone is to add support for Helm v4 to helm-controller, and to reduce the mean time to recovery (MTTR) for app deployments.

• OCI integrations

  • Add support for verification with cosign v3

• Helm integrations

  • Add support for Helm v4 to helm-controller
  • Reduce the mean time to recovery (MTTR) for Helm release

• Kustomize integrations

  • Reduce the mean time to recovery (MTTR) in case of a failed deployment

• Alerting integrations

  • Support ArtifactGenerator notifications

• Source extensions

  • Allow ExternalArtifact as a source in ArtifactGenerator
  • Allow HelmChart as a source in ArtifactGenerator
  • Implement tarball extraction in ArtifactGenerator

• Conformance testing

  • End-to-end testing for Kubernetes 1.35

• EOL and Deprecations

  • End support for Flux v2.5.x
  • End support for Kubernetes v1.32.x
  • Remove deprecated APIs in group source.toolkit.fluxcd.io/v1beta2
  • Remove deprecated APIs in group kustomize.toolkit.fluxcd.io/v1beta2
  • Remove deprecated APIs in group helm.toolkit.fluxcd.io/v2beta2

v2.9 (Q2 2026)

Status: Provisional

The primary goal of this milestone is to add support for Helm Chart API v3, and extend Flux server-side apply with field ignore rules.

• Helm integrations

  • Add support for Helm Chart API v3 to source-controller
  • Add support for Helm Chart API v3 to helm-controller

• Kustomize integrations

  • Extend Server-Side Apply with field ignore rules

• Alerting integrations

  • Add support for posting comments to GitHub/GitLab

• Source extensions

  • SDK for facilitating the development of 3rd party controllers based on the ExternalArtifact API

• Conformance testing

  • End-to-end testing for Kubernetes 1.36

• EOL and Deprecations

  • End support for Flux v2.6.x
  • End support for Kubernetes v1.33.x
  • Remove deprecated APIs in group image.toolkit.fluxcd.io/v1beta2
  • Remove deprecated APIs in group notification.toolkit.fluxcd.io/v1beta2

v2.10 (Q3 2026)

Status: Provisional

The primary goal of this milestone is to make a generally available release for the Flux Alerting APIs.

• Alerting integrations

  • Promote the Event API to v1
  • Promote the Alert API to v1
  • Promote the Provider API to v1

• Source extensions

  • Build external artifacts locally with flux build artifact generator

• Conformance testing

  • End-to-end testing for Kubernetes 1.37

• EOL and Deprecations

  • End support for Flux v2.7.x
  • End support for Kubernetes v1.34.x
  • Deprecate APIs in group notification.toolkit.fluxcd.io/v1beta3

Request for comments

The RFC process provides a consistent and controlled path for substantial changes to enter Flux.

To keep track of the Flux project’s current direction and future plans, please see the following RFCs:

• RFC-0001 Memorandum on the authorization model
• RFC-0002 Flux OCI support for Helm
• RFC-0003 Flux OCI support for Kubernetes manifests
• RFC-0004 Block insecure HTTP connections across Flux
• RFC-0005 Artifact Revision format and introduction of Digest
• RFC-0006 Flux CDEvents Receiver
• RFC-0007 Passwordless authentication for Git repositories
• RFC-0008 Custom Event Metadata from Annotations
• RFC-0009 Custom Health Checks for Kustomization using Common Expression Language(CEL)
• RFC-0010 Multi-Tenant Workload Identity
• RFC-0011 OpenTelemetry Tracing
• RFC-0012 External Artifact API