containers-roadmap
containers-roadmap copied to clipboard
aws
[EKS] [fargate] [request]: Support graviton architecture for fargate nodes spawned by EKS
Currently, there seems to be no way to choose the architecture for fargate nodes spawned by EKS clusters.
This could be configurable in the fargate profile, or even better, transparently by setting the kubernetes.io/arch=arm64 nodeselector in kubernetes deployments
Community Note
- Please vote on this issue by adding a 👍 reaction 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 What do you want us to build?
Which service(s) is this request for? This could be Fargate, ECS, EKS, ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
Are you currently working around this issue? How are you currently solving this problem?
Additional context Anything else we should know?
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Got 90% through the way of configuring EKS Fargate today and then realised there's no arm64 support. Didn't even consider that this would be left out! Is there any timeline for this? We dropped x86_64 builds for some services a while ago to simplify CI.
Got 90% through the way of configuring EKS Fargate today and then realised there's no arm64 support. Didn't even consider that this would be left out! Is there any timeline for this? We dropped x86_64 builds for some services a while ago to simplify CI.
I'm in similer situation. Walked through almost all of CI pipeline settings, but found out there is no support on EKS cluster.
Got 90% through the way of configuring EKS Fargate today and then realised there's no arm64 support. Didn't even consider that this would be left out! Is there any timeline for this? We dropped x86_64 builds for some services a while ago to simplify CI.
btw I did the same thing. Went all the way to converting my images to arm64 arch only to find out it's not possible to run them with fargate on EKS :(
If they can do this and somehow drop the cost for the control plane I could finally move all my personal projects off DigitalOcean and into AWS. (Which I use for all my professional work)
Yes, the organization I'm working with would really like to have this feature. We can run everything ARM, and such could take advantage of the lower-cost compute. Bummer that it isn't available. :-(
We are also 100% ARM compatible, are awaiting this support, and are evaluating switching off Fargate if it isn't supported soon.
I was disappointed to learn that arm is not available in Fargate profile. My development machine is also Arm-based, and I'd like to have it all. In addition, it would be a waste to have CI build both x86 and arm.
having access to this could significantly assist in our journey of embracing graviton: currently our CI/CD system is using managed runners which is extremely convenient, but arm64 runners are not available. with EKS-fargate-arm64 we could achieve similar fidelity by moving our container builds to EKS using Kaniko from the existing CI workflow without having to maintain and scale runners
Commenting that I would also like to see this feature as I got 90% of the way to configuring running pods just to see that ARM isn't supported :(
coredns also recently fixed builds for arm and today cut the first release that built arm images.
- https://github.com/coredns/coredns/issues/5842#issuecomment-1375738388
- https://github.com/coredns/coredns/releases/tag/v1.10.1
Considering coredns is a long-running cluster service, switching it over to graviton/arm would make for easy cost savings.
Commenting that I would also like to see this feature as I got 90% of the way to configuring running pods just to see that ARM isn't supported :(
Same here, would love to see this, as ECS already has it!
Would love to be able to burst into Fargate ARM fabric within EKS. It would enable some very efficient architectures.
++1 Would love to be able to burst into Fargate ARM fabric with EKS for short term compute intensive tasks.
A lot of companies in Korea are hesitant to switch arch to FARGATE. just because it doenst support ARM architectures
Just to chime in here, we abandoned Fargate for Managed Node Groups and ARM64 was the straw that broke that camel's back.
Disappointed for this one not to appear at re:invent - it just seems so odd for it to have existed happily for ECS for so long to still be missing from EKS.
me too
On Mon, 4 Dec 2023 at 18:38 Nicolai Antiferov @.***> wrote:
image.png (view on web) https://github.com/aws/containers-roadmap/assets/75987872/3da40571-8103-4d70-993e-daee4eaa3e4e
— Reply to this email directly, view it on GitHub https://github.com/aws/containers-roadmap/issues/1629#issuecomment-1838574266, or unsubscribe https://github.com/notifications/unsubscribe-auth/AELPDJKIUS2BZM3CUD6YKODYHXBVVAVCNFSM5MGIPH2KU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBTHA2TONBSGY3A . You are receiving this because you commented.Message ID: @.***>