-
Notifications
You must be signed in to change notification settings - Fork 335
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
Update timetable and set Flux v1 sunset for November 1st #1156
Conversation
Signed-off-by: Stefan Prodan <[email protected]>
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 think this is a reasonable timetable given that v2 has been used in production for quite some time now.
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.
👍 from me for this
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.
Plenty of time has been given to move to Fluxv2. I know of some of the issues making Helm Operator work with newer k8s versions, and its not worth the time.
Given that Flux v1 and helm-operator dependencies are pinned to EOL versions (Kubernetes 1.21, Kustomize 3.8), which cannot be upgraded without causing regressions or a cascading amount of changes to the codebase, I propose we archive both projects on 1st Nov 2022, right after Kubernetes v1.22 reaches end-of-life on 28th Oct 2022.
Migration timetable updates:
Refs: