Open
Description
Description
What problem are you trying to solve?
Currently, if you set the --isolated-vpc
setting, you won't get any pricing information discovered and Karpenter will fully rely on statically created pricing information that is shipped with Karpenter on each release. We made this decision since the AWS price list API is only available in a smaller set of regions; however, this API is only used to discover on-demand pricing information. Spot pricing information is discovered through EC2, which does have a VPC private endpoint.
We can allow spot pricing information to be retrieved, even when you have the --isolated-vpc
setting set.
- Please vote on this issue by adding a 👍 reaction 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
Activity