Use EC2 DescribeInstanceTypes API instead of parsing pricing API

[AustinSiu]

Which component are you using?:
Cluster Autoscaler

Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:

CA maintains code to handle instance filtering and parsing from EC2 pricing API.

Describe the solution you'd like.:

Update existing API call with a filterable list through EC2's DescribeInstanceTypes API to simplify the logic.

Describe any alternative solutions you've considered.:

Additional context.:

[gjtempleton]

/area provider/aws

[sbs2001]

@AustinSiu are you working on a patch for this ? If not I'd like to submit one :)

[AustinSiu]

@AustinSiu are you working on a patch for this ? If not I'd like to submit one :)

@sbs2001 I'm actively working on a patch for this. Thanks for checking!

[jaypipes]

@gjtempleton honestly, I don't know why we didn't go this route when the EC2 DescribeInstanceTypes API was released in November 22, 2019. I'm supportive of this approach and @AustinSiu's PR looks solid to me.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[gjtempleton]

Addressed by #4468 which has now been merged and released.
/close

[k8s-ci-robot]

@gjtempleton: Closing this issue.

In response to this:

Addressed by #4468 which has now been merged and released.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.