Fix ASG dependencies, use AWS SDK native struct for warmpool options

[rsafonseca]

Addresses #15289
Uses AWS SDK builtin struct, so it will be easier to add additional options, and will the struct will contain any future options that AWS might add to the warmpool.

[k8s-ci-robot]

Hi @rsafonseca. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign justinsb for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[olemarkus]

/ok-to-test

I wrote an integration test for this one. Let me push that commit to this branch as well.

[olemarkus]

/test pull-kops-e2e-k8s-aws-calico

[rsafonseca]

I've added you to the repo @olemarkus, feel free to push to the branch :)

[olemarkus]

The PR has maintainer edits enabled. But thanks anyway :)

[olemarkus]

Can you look at the test failure?

[jim-barber-he]

I seems like the following has fixed the issue?
#15722

[k8s-ci-robot]

PR needs rebase.

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.

[aramhakobyan]

@rsafonseca @olemarkus @jim-barber-he @crigor - I see this fix has not been backported to 1.26 version - could you please backport it in the 1.26 and create new 1.26.* release ?

Error:

13:38:51  I0108 12:38:51.472966     445 executor.go:111] Tasks: 140 done / 143 total; 1 can run
13:38:51  I0108 12:38:51.737345     445 executor.go:155] No progress made, sleeping before retrying 1 task(s)
13:39:03  Error: error running tasks: deadline exceeded executing task WarmPool/default.fa2c826d5. Example error: waiting for ASG to become ready

[k8s-ci-robot]

@rsafonseca: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-test	74089be	link	true	/test pull-kops-test
pull-kops-kubernetes-e2e-ubuntu-gce-build	74089be	link	true	/test pull-kops-kubernetes-e2e-ubuntu-gce-build
pull-kops-verify-hashes	74089be	link	true	/test pull-kops-verify-hashes

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten