This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Why should I migrate to Flux v2? #3467
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kingdonb
pushed a commit
to kingdonb/flux2
that referenced
this pull request
Apr 19, 2021
c641393 to
74ac370
Compare
|
👍 LGTM |
added 2 commits
April 22, 2021 08:16
Closes fluxcd/flux2#1290 Signed-off-by: Kingdon Barrett <kingdon@weave.works>
Flux v1 is in Maintenance. Upgrade/migrate to Flux v2 Signed-off-by: Kingdon Barrett <kingdon@weave.works>
74ac370 to
89a5a3f
Compare
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a prominent note to the top of the Flux v1 FAQ, exhorting users to go ahead and start moving on to Flux v2 yet again. If you are reading the Flux v1 FAQ at this time, the top FAQ entry should be boldly and prominently that Flux v1 is growing nearer to the end of its Maintenance Mode support period.
We will follow the migration support timetable as established in https://toolkit.fluxcd.io/migration/timetable/
We should periodically review the details on that timetable page and evaluate the progress, noting any updates as they arrive, and checking for current and correctness of the support and archive timetable's estimated dates.
It seems to me there's some space between "upgrading now is strongly recommended" and "Flux v1 is officially superceded"