aws / aws/containers-roadmap

[EKS] [request]: Enable Worker Orchestration in separate VPC to Cluster

Open
#153 17 comments 49 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

**Tell us about your request**
Currently it does not seem possibly to orchestrate workers in different VPCs to the EKS control plane.

**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?**
We currently isolate development environments in separate VPCs, and are looking to adopt EKS. The cleanest pattern for us would be to stand up one EKS cluster that can embed workers into each of the development environment VPCs.

**Are you currently working around this issue?**
Currently we would have to stand up separate EKS clusters per environment.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the EKS worker-orchestration and VPC requirements described in this issue, including the current separate-cluster workaround. Done means establishing whether one EKS cluster can place workers in multiple development VPCs and documenting the supported approach or remaining limitation.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.