aws / aws/containers-roadmap

[EKS] [addon]: Support Flux V2 in EKS addons

Open
#1,593 11 comments 145 reactions 0 assignees View on GitHub
EKS EKS Add-Ons
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Please add Flux V2 in EKS addons. There is a helm chart now so should be relatively easy. See https://github.com/fluxcd-community/helm-charts

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Need to get flux installed reliably and simply in the EKS cluster in a way that is easy to upgrade without breaking all the installed resources by flux.
**Are you currently working around this issue?**
Flux and kubernetes provider in terraform but this is unreliable and can fail silently.
Flux have a command line flux bootstrap but this needs organisational access to the github repo and is unnecessary once a git repo has been setup.

**Additional context**
Once flux is installed then flux can automatically install the rest of the kubernets resources so its a big win in eks can do this in the addons.

**Attachments**
See https://github.com/fluxcd-community/helm-charts for the charts

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the repository's existing EKS addon support and the Flux Community Helm charts linked in the issue. Define done as Flux V2 being installable and upgradeable through EKS addons without breaking resources; the issue names no files, tests, or implementation entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes, terraform
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.