[EKS] [request]: Support LLQ on EKS worker nodes
- 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**
Enable LLQ on EKS Worker Nodes.
Related Issue: https://github.com/amzn/amzn-drivers/issues/142
**Which service(s) is this request for?**
This could be Fargate, EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Enable LLQ for EKS clusters to handel large packets
**Are you currently working around this issue?**
NA
**Additional context**
NA
**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.)
Contributor guide
Research direction
Start by reading the related issue, amzn/amzn-drivers#142, and clarify what LLQ support means for EKS worker nodes and large packets. The issue names no repository files, tests, or implementation entry point. Done would require an agreed implementation scope and verified LLQ support for the stated EKS or Fargate service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100