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: Completed on 2025-02-20 (v2.5.0 changelog)
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
Webhook integrations
Troubleshoot helpers
Conformance testing
EOL and Deprecations
- End support for Flux v2.2.x
- End support for Kubernetes v1.29.x
v2.6 (Q2 2025)
Status: In Progress
The primary goal of this milestone is to make a generally available release for the Flux OCI Artifacts APIs and add support for object-level workload identity authentication for container registries.
OCI artifacts integrations
- Promote the
OCIRepository
API tov1
- Promote to stable the Flux CLI commands:
flux push artifact
flux tag artifact
flux get artifact
flux diff artifact
flux list artifacts
- Cache registry credentials for cloud providers
- Introduce object-level workload identity for OCIRepository
- Promote the
Image automation
Git integrations
Kustomize integrations
Alerting integrations
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
source.toolkit.fluxcd.io/v1beta2
v2.7 (Q3 2025)
Status: Provisional
The primary goal of this milestone is to make a generally available release for the Flux image automation APIs, and make Flux server-side apply compatible with Kubernetes Vertical Pod Autoscaler (VPA).
Image automation
- Promote the
ImageUpdateAutomation
API tov1
- Promote the
ImageRepository
API tov1
- Promote the
ImagePolicy
API tov1
- Promote the
Kustomize integrations
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
image.toolkit.fluxcd.io/v1beta2
- Remove deprecated APIs in group
helm.toolkit.fluxcd.io/v2beta1
- Remove deprecated APIs in group
image.toolkit.fluxcd.io/v1beta1
- Remove deprecated APIs in group
source.toolkit.fluxcd.io/v1beta1
- Remove deprecated APIs in group
kustomize.toolkit.fluxcd.io/v1beta1
- Remove the
autologin
deprecated flags fromimage-reflector-controller
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 ofDigest
- 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 External Artifact API
- RFC Flux Bootstrap for OCI-compliant Container Registries