# Roadmap !!! hint "Work in Progress" We will be building the roadmap together with the Flux community, our end-users and everyone who is interested in integrating with us. So a lot of this is still TBD - read this as our shopping list of ideas after some brainstorming as Flux maintainers. ## The road to Flux v2 ### Flux read-only feature parity [= 80% "80%"] This would be the first stepping stone: we want the GitOps Toolkit to be on-par with today's Flux in [read-only mode](https://github.com/fluxcd/flux/blob/master/docs/faq.md#can-i-run-flux-with-readonly-git-access) and [FluxCloud](https://github.com/justinbarrick/fluxcloud) notifications. Goals - Offer an in-place migration tool for those that are using Flux in read-only mode to synchronize plain manifests - Offer a migration guide for those that are using Flux in read-only mode to synchronize Kustomize overlays - :material-check-bold: [Offer a dedicated component for forwarding events to external messaging platforms](https://toolkit.fluxcd.io/guides/notifications/) Non-Goals - Migrate users that are using Flux to run custom scripts with `flux.yaml` - Automate the migration of `flux.yaml` kustomize users Tasks - [x] Design the events API - [x] Implement events in source and kustomize controllers - [x] Make the kustomize-controller apply/gc events on-par with Flux v1 apply events - [x] Design the notifications and events filtering API - [x] Implement a notification controller for Slack, MS Teams, Discord, Rocket - [x] Implement Prometheus metrics in source and kustomize controllers - [ ] Review the git source and kustomize APIs - [ ] Implement the migration command in tk - [ ] Create a migration guide for `flux.yaml` kustomize users - [ ] Include [support for SOPS](https://github.com/fluxcd/toolkit/discussions/156) ### Flux image update feature parity [= 0% "0%"] Goals - Offer components that can replace Flux v1 image update feature Non-Goals - Maintain backwards compatibility with Flux v1 annotations Tasks - [ ] [Design the image scanning and automation API](https://github.com/fluxcd/toolkit/discussions/107) - [ ] Implement an image scanning controller - [ ] Design the automation component - [ ] Implement the image scan/patch/push workflow - [ ] Integrate the new components in the toolkit assembler - [ ] Create a migration guide from Flux annotations ## The road to Helm Operator v2 ### Helm v3 feature parity [= 70% "70%"] Goals - Offer a migration guide for those that are using Helm Operator with Helm v3 and charts from Helm and Git repositories Non-Goals - Migrate users that are using Helm v2 Tasks - [x] Implement a Helm controller for Helm v3 covering all the current release options - [x] Discuss and design Helm releases based on source API: * [x] Providing values from sources * [x] Conditional remediation on failed Helm actions * [x] Support for Helm charts from Git - [x] Review the Helm release, chart and repository APIs - [x] Implement events in Helm controller - [x] Implement Prometheus metrics in Helm controller - [x] Implement support for values from `Secret` and `ConfigMap` resources - [ ] [Implement conditional remediation on (failed) Helm actions](https://github.com/fluxcd/helm-controller/issues/41) - [ ] [Implement support for Helm charts from Git](https://github.com/fluxcd/source-controller/issues/56) - [ ] [Implement support for referring to an alternative chart values file](https://github.com/fluxcd/helm-controller/issues/4) - [ ] Create a migration guide for Helm Operator users