Flux Roadmap

Production readiness

The Flux latest beta and stable APIs (including their reconcilers) are well tested and safe to use in production environments. The beta APIs will be replaced in time with stable versions.

To learn more about Flux supported versions and release cadence, please see the Flux release process.

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.5 (Q1 2025)

Status: In Progress

The primary goal of this milestone is to integrate GitHub App for Git repositories authentication and to extend Flux functionality with Common Expression Language(CEL) support.

Git integrations
Kustomize integrations
Alerting integrations
- Custom Event Metadata from Annotations
Webhook integrations
- Implement Receiver resource filtering with CEL
Troubleshoot helpers
- Implement flux debug helmrelease --show-values
- Implement flux debug kustomization --show-vars
Conformance testing
- End-to-end testing for Kubernetes 1.32
- End-to-end testing for GitHub App auth
EOL and Deprecations
- End support for Flux v2.2.x
- End support for Kubernetes v1.29.x
- Remove deprecated APIs in group source.toolkit.fluxcd.io/v1beta1
- Remove deprecated APIs in group kustomize.toolkit.fluxcd.io/v1beta1
- Remove deprecated APIs in group helm.toolkit.fluxcd.io/v2beta1

v2.6 (Q2 2025)

Status: Provisional

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

Image automation
- Promote the ImageUpdateAutomation API to v1
- Promote the ImageRepository API to v1
- Promote the ImagePolicy API to v1
- Add support for updating OCI digests
OCI artifacts integrations
- Cache registry credentials for cloud providers
Alerting integrations
- Add support for GitHub App auth to Provider API
Conformance testing
- End-to-end testing for Kubernetes 1.33
EOL and Deprecations
- End support for Flux v2.3.x
- End support for Kubernetes v1.30.x
- Deprecate APIs in group image.toolkit.fluxcd.io/v1beta2
- Remove deprecated APIs in group image.toolkit.fluxcd.io/v1beta1

v2.7 (Q3 2025)

Status: Provisional

The primary goal of this milestone is to make a generally available release for the Flux OCI Artifacts APIs and make Flux server-side apply compatible with Kubernetes Vertical Pod Autoscaler (VPA).

OCI artifacts integrations
- Promote the OCIRepository API to v1
- Enhance OCI Artifact support
- Add support for layer extraction from OCI artifacts with ImageIndex
Kustomize integrations
- Extend ssa.Apply with field ignore rules
Conformance testing
- End-to-end testing for Kubernetes 1.34
EOL and Deprecations
- End support for Flux v2.4.x
- End support for Kubernetes v1.31.x
- Deprecate APIs in group source.toolkit.fluxcd.io/v1beta2

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 current direction and future plans, please see 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 Custom Health Checks for Kustomization using Common Expression Language(CEL)
RFC Flux Bootstrap for OCI-compliant Container Registries