AWS teams struggle to control VPC subnet capacity and topology
AWS infrastructure and Kubernetes platform engineers need finer control over VPC subnet placement and configuration. Reports describe Karpenter selecting subnets that are running low on IPs, and CDK users wanting more control over CIDRs, subnet tags, and eligible availability zones; changing a deployed VPC's AZ count can also require replacement or migration. The requests date from 2020–2022, so it is unclear whether these gaps persist or how widespread they are today.
For AWS infrastructure and Kubernetes platform engineers. Mentioned from Nov 2017 to Nov 2022 on GitHub.
7 different people described this problem in 5 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 7.4/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Also using spot and running out of ips. I have 3 subnets each in their own AZ and it mostly only allocates ips in the first AZ
Karpenter should select a subnet with available IPs from all subnets available for EKS. We are facing a issue where subnet from one AZ is running out of IPs
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 5 more quotes from people who have this problem
- Current workarounds, existing solutions and risks