Add Tinkerbell Cluster Autoscaler E2E Test

[jonathanmeier5]

Issue #, if available:
#5883

Description of changes:
This PR adds an end to end test verifying that cluster autoscaler works on tinkerbell.

Testing (if applicable):
Ran e2e test manually and verified success.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (79c297c) 71.70% compared to head (14e7ddd) 71.69%.
Report is 59 commits behind head on main.

❗ Current head 14e7ddd differs from pull request most recent head 62adf94. Consider uploading reports for the commit 62adf94 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5884      +/-   ##
==========================================
- Coverage   71.70%   71.69%   -0.01%     
==========================================
  Files         531      531              
  Lines       41121    41121              
==========================================
- Hits        29486    29483       -3     
- Misses       9981     9983       +2     
- Partials     1654     1655       +1     

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jonathanmeier5]

/test-all

[jonathanmeier5]

/test all

[ddjjia]

can we run CheckCuratedPackagesCredentials there?

[ddjjia]

why need to set cp node number? I just don't see it else where so if it's default to 1?

[jonathanmeier5]

I was following other packages examples here. Searching for WithControlPlaneHardware(1 I do see some other examples, particularly for packages but also for some other types of tests.

I kind of prefer it explicit like this, but if you'd rather I take it out I can do that, just let me know.

[eks-distro-bot]

[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 ask for approval from jonathanmeier5. 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

[eks-distro-bot]

@jonathanmeier5: 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
eks-anywhere-presubmit	62adf94	link	true	/test eks-anywhere-presubmit
eks-anywhere-cli-attribution-presubmit	62adf94	link	true	/test eks-anywhere-cli-attribution-presubmit
eks-anywhere-e2e-presubmit	62adf94	link	true	/test eks-anywhere-e2e-presubmit
eks-anywhere-e2e-validate-tinkerbell-hardware-presubmit	62adf94	link	true	/test eks-anywhere-e2e-validate-tinkerbell-hardware-presubmit

Full PR test history. Your PR dashboard.

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.