IssueRaiser

[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 <!-- Please keep this note for the community --> ### 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 <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **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 rig

Posted by mfeldheim on Jan 18, 2022, 5:58 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

support (Sysadmin)

[EKS] [fargate] [request]: Support graviton architecture for fargate nodes spawned by EKS

mfeldheimJan 18, 2022, 5:58 AM

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 <!-- Please keep this note for the community --> ### 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 <!-- Thank you for keeping this note for the community --> <!-- **Security disclosures** If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions [here](https://aws.amazon.com/security/vulnerability-reporting/) or [email AWS security directly](mailto:aws-security@amazon.com). --> **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 rig

Comments (0)

No comments yet. Start the discussion.

Comment on this issue