New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flux 2020 Annual Review #511
Conversation
guides and integrations around. | ||
* Cloud vendors and industry partners integrate with Flux and are | ||
watching GOTK development closely. | ||
* As Flux is in a very interesting phase of its development right |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you elaborate on "some while" - is it months, years? Or is it something that can't be estimated at this moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Low numbers of months. There's a timeline here; we're operating a migration window during which both Flux v1 and v2 are maintained, but expect contributions to Flux v1 to dwindle quickly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To build on @squaremo 's link to the v2 roadmap, here is an issue fluxcd/flux#3320 with a more specific note on dates for v1:
Once we have reached feature-parity across all current feature sets… we will continue to support Flux v1 and Helm Operator v1 for 6 more months.
Exactly what "support" during that phase will mean here is not yet officially defined – when it will be bug fixes only (no new features), and security fixes only (no more bug fixes), etc. For now, that issue says this:
Flux (v1) is still being maintained and supported, it will just take a bit longer until we get around to issues and PRs. Critical bug fixes have our priority, we are going to be hesitant and look very careful at anything that will extend functionality.
Until that time, there will still be contributions to both v1 and v2, with a progressive tapering off from v1 until only v2 is supported.
This is the Flux project's first review, so there are no goals already | ||
on record. However, there are some measures of progress: | ||
|
||
* We have been talking to users and customers a lot. The Flux |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Developer advocacy for GitOps in the community is the great effort. Thank you for doing that!
* We have been talking to users and customers a lot. The Flux | ||
community was instrumental in running the [GitOps | ||
Days](https://www.gitopsdays.com/) event, for example. | ||
* We started experimentation in the GitOps Toolkit, designed the APIs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also include the link to the Flux v2 roadmap? Assuming it's this link https://toolkit.fluxcd.io/roadmap/#the-road-to-flux-v2; if not - please include the most recent one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the one!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've included a link to the roadmap directly below this.
LGTM for Sandbox annual review |
JFYI #567 is up for review now too… |
This was accepted in the December 8 meeting. |
Please find enclosed the Flux project annual review for year ending August 2020.