Skip to content

Use dynamic instance lists in VPC resource controller #620

@randiskull

Description

@randiskull

Is your feature request related to a problem? Please describe.
When AWS releases a new instance type there is a 30 day delay before Karpenter users are able to test on the new instance types. An internal AWS API is a bottleneck for EKS Optimized AMI, Karpenter, and the vpc-resource controller.

Describe the solution you'd like
I would like the ability to test GA instance types in Karpenter on Day 1 in supported regions, with the ability to discover all instance specifications and limits to consider for configuration planning.

Describe alternatives you've considered
Alternative approaches require engagement with AWS service team to request for expedited support or version updates, or to run Codegen across multiple repos to populate missing values with public API.

Additional context
Pod Security Groups (SGPP) require existence of values populated in the instance lists so they take a dependency on the internal AWS API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions