[EKS] [request]: Multi VPC Worker Node Support
- 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**
Multip VPC Worker Nodes
**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?**
It would be helpful if we can use single EKS cluster with multiple VPC worker nodes. this not only fesibal the options where we are running diffrent enviroments for testing, staging we have to manage seperate EKS cluster which is an hetic task. by using multiple VPC Node support we can combine all them into single EKS culster which is helpful for development enviomrnets.
**Are you currently working around this issue?**
nope.
Contributor guide
Research direction
The issue requests support for worker nodes across multiple VPCs in one EKS cluster. Start by clarifying the desired architecture and constraints with the maintainers; done would require an agreed implementation path and confirmed EKS support for the requested setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100