Autoscaler: AWS CN Pricing endpoint

[duweihello]

https://github.com/kubernetes/autoscaler/blob/ca6bbc96a2ef40a46043a23425bf242c5273e799/cluster-autoscaler/cloudprovider/aws/aws_util.go#L35
the pricing API is not support AWS CN regions, is there any alternative way to pass it?

[BellonXiao]

Same issue here with 1.17.2:
aws_util.go:86] Error unmarshalling https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/cn-north-1/index.json, skip..
aws_cloud_provider.go:363] Failed to generate AWS EC2 Instance Types: unable to load EC2 Instance Type list

endpoint for AWS CN (both regions) should be https://pricing.cn-north-1.amazonaws.com.cn/offers/v1.0/cn/AmazonEC2/current/index.json

[gjtempleton]

I think the ideal way to resolve this is to move away from the use of the pricing API. Alternatively you should now (as of the latest releases) be able to use the hardcoded list by using the aws-use-static-instance-list flag set to true as it'll no longer attempt to call the pricing API.

I'd meant to move away from the pricing APIs to resolve #2696 which includes some of the other issues with the use of the Pricing API and never got around to it earlier in the year. I'll see if I can find the time to pick this work back up.

[greenu]

related issue #3076

[momkeller]

I am also running into this issue in cn-north-1 using AS 1.15.7. Is there a workaround or projected fix date?

[marcheil]

Using 1.17.2,So what is the work around here for clusters that do not have internet access? How do we set the aws-use-static-instance-list flag?

[Jeffwan]

I approve PR https://github.com/kubernetes/autoscaler/pull/3528.
Let's wait for the next release

[jumping]

Is there any scheduler to merge the fix into some release ?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten