Skip to content
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

Eksctl gitops v1 deprecation #2963

Closed
Callisto13 opened this issue Dec 17, 2020 · 4 comments · Fixed by #4471
Closed

Eksctl gitops v1 deprecation #2963

Callisto13 opened this issue Dec 17, 2020 · 4 comments · Fixed by #4471
Assignees

Comments

@Callisto13
Copy link
Contributor

Callisto13 commented Dec 17, 2020

What is this?

The eksctl tool provides users a handy way to set up gitops in their cluster with theeksctl enable repo command.

Flux v1 (the gitops mechanism deployed into clusters by eksctl) has been in maintenance mode since October 2020, and the team have been working hard on v2, which is very exciting 🎉 . So we want to get in on that 😄 .

This means that we have integrated Flux v2 alongside the now deprecated gitops configuration as provided by eksctl 😎 .

As such, we plan to remove eksctl's v1 integration (eksctl enable repo). This will include the removal of Quickstart profiles (eksctl enable profile), which is a feature leveraging Flux v1 mechanisms.

enable repo, generate profile and enable profile are now deprecated. Please use enable flux.

Timeline 🕐

The timeline for removing the option to deploy Flux v1 within eksctl configuration is currently planned to line up with the EOL of Flux v1 (~6 months from 12.02.21). Any changes to the eksctl plan will be published here. Flux v2 now has parity with v1, which means we will remove eksctl support for Flux v1 as soon as Flux v2 reaches GA. A specific date will be announced soon.

I have questions, who do I go to? ❓

For questions about this deprecation in eksctl and the v2 integration please comment on this issue or the eksctl v2 feature issue.

For all general questions concerning eksctl and Flux/gitops integrations, please open an issue in this repo.

Please do not go to the Flux maintainers/community with eksctl-related concerns.

I have an issue with the current gitops integration (v1) 🤯

We are still maintaining that codepath, but at a lower priority. Critical issues and bugs will still be prioritised, while embellishments will be declined. However, we strongly recommend that you start using Flux v2 (enable flux).

I am super keen, how do I start using Flux v2 right now!? 💥

You can manually (as in nothing to do with eksctl) set up Flux v2 in existing clusters by following their documentation. There are also some lovely migration guides ✨ .

Update: from eksctl version 0.53.0 you can deploy Flux v2 to your cluster as part of an eksctl create cluster command. Work is still experimental and ongoing here, but we welcome feedback 😄 .

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jan 18, 2021
@Callisto13
Copy link
Contributor Author

sigh just be cool, stale-bot

@Callisto13
Copy link
Contributor Author

Callisto13 commented Feb 4, 2021

Note: when coming round to remove v1 stuff, simply rg "FLUX V1 DEPRECATION NOTICE" to find the right bits.

@Himangini
Copy link
Collaborator

We need to remove all the deprecated commands as part of this.

@aclevername aclevername self-assigned this Nov 16, 2021
@Himangini Himangini unpinned this issue Feb 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants