Fixed bug with missing taint translation layer between AWS EKS format and Kubernetes format

[wcarlsen]

What type of PR is this?

/kind bug

What this PR does / why we need it:

This PR fixes a bug between AWS EKS API understanding of Kubernetes taints and normal Kubernetes understanding of taints by introducing a translation method. Since the AWS API response when calling DescribeNodegroup have taints in the format of NO_SCHEDULE instead of NoSchedule as an example.

Which issue(s) this PR fixes:

Fixes #6481

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: wcarlsen / name: Willi Carlsen (e27ae68, bb81dd3, 74a5500)

[k8s-ci-robot]

Welcome @wcarlsen!

It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-triage-robot]

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle stale

[abstrask]

/remove-lifecycle stale

[x13n]

/assign @gjtempleton @drmorr0

Can (one of) you take a look?

[wcarlsen]

So anything we can do to get the ball rolling on this one?

[drmorr0]

Just a couple minor comments, will approve when those are fixed.

[drmorr0]

/lgtm

[drmorr0]

/approved

[abstrask]

/approved

Should this be /approve?

Approvers can indicate their approval by writing /approve in a comment

[drmorr0]

d'oh. thank you.

[drmorr0]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: drmorr0, wcarlsen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cluster-autoscaler/cloudprovider/aws/OWNERS [drmorr0]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[abstrask]

The fix is included in release 1.31.0 🥳