Pricing Endpoints in EKS Private Clusters
### Tell us about your request Existing implementations automatically select the pricingAPIRegion by region. https://github.com/aws/karpenter/blob/077c099b4419d0caac447904d9ffae1d871e37b9/pkg/cloudprovider/aws/pricing.go#L86-L91 However, I would like to determine the pricingAPIRegion myself without following this logic. ### Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? This problem occurs, for example, when karpenter is used in a region starting with "ap-" and the use of ap-south-1 is restricted by [AWS SCPs](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html). Removing the restriction on the use of ap-south-1 by AWS SCPs would solve this problem, but we do not want to do that as much as possible because it would increase the security risk. Instead, we want to use us-east-1 for pricingAPIRegion even if the region starts with "ap-". ### Are you currently working around this issue? No, we have not been able to work around this issue. ### Additional Context _No response_ ### Attachments _No response_ ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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
Posted by hekki on Oct 5, 2022, 7:55 AM
Tags
Related issues
- >Beef is already too expensive for most people.
- I gave this a go a couple of years ago.
- I haven't seen any use cases around me, although I'm not that advanced user.
- [BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
- > Unfortunately it doesn't offer free hosting for hobbyists.
- Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
pricing (Software)
>Beef is already too expensive for most people.
I gave this a go a couple of years ago.
I haven't seen any use cases around me, although I'm not that advanced user.
[BUG] Pro Max 5x Quota Exhausted in 1.5 Hours Despite Moderate Usage
> Unfortunately it doesn't offer free hosting for hobbyists.
Still the same HID remapping project from last month (I was hoping to be done by now, but hardware is hard): https://github.co...
This criticism seems like a complete non-sequitur to me.
Bring back the GitHub Copilot in the CLI commands to not break workflows
Pricing Endpoints in EKS Private Clusters
### Tell us about your request Existing implementations automatically select the pricingAPIRegion by region. https://github.com/aws/karpenter/blob/077c099b4419d0caac447904d9ffae1d871e37b9/pkg/cloudprovider/aws/pricing.go#L86-L91 However, I would like to determine the pricingAPIRegion myself without following this logic. ### Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? This problem occurs, for example, when karpenter is used in a region starting with "ap-" and the use of ap-south-1 is restricted by [AWS SCPs](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html). Removing the restriction on the use of ap-south-1 by AWS SCPs would solve this problem, but we do not want to do that as much as possible because it would increase the security risk. Instead, we want to use us-east-1 for pricingAPIRegion even if the region starts with "ap-". ### Are you currently working around this issue? No, we have not been able to work around this issue. ### Additional Context _No response_ ### Attachments _No response_ ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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
Comments (0)
No comments yet. Start the discussion.