Automatically update/determine limits
dougbyrne opened this issue · 5 comments
What would you like to be added:
A method to automatically discover limits for new instance types so that they can be used as soon as they are made available by AWS.
A small workaround would be to ensure the make generate-limits command is run as a part of the release workflow, but still requires an update of the CNI plugin for users to use new instance types.
Why is this needed:
A user managing their cluster with karpenter may have new instance types selected as soon as they are made available by AWS, but until they are added to https://github.com/aws/amazon-vpc-cni-k8s/blob/master/misc/eni-max-pods.txt they can't be used, leading to a failed node.
This issue may be related: aws/amazon-vpc-resource-controller-k8s#98
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days
Unstale
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days
Issue closed due to inactivity.