Update CI to use 1.32 eks and kops clusters

[ElijahQuinones]

What type of PR is this?

/kind cleanup

What is this PR about? / Why do we need it?

This PR updates our CI to use k8s 1.32 when creating clusters using kops and eksctl

How was this change tested?

CI and running make cluster/create with change to verify 1.32 cluster is created

Does this PR introduce a user-facing change?

NONE

/hold

holding until local testing is done

[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 ask for approval from elijahquinones. For more information see the 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

[github-actions]

Code Coverage Diff

This PR does not change the code coverage

[ElijahQuinones]

When running locally run in to Error: cannot determine hash for "https://artifacts.k8s.io/binaries/kops/1.32.0-beta.1/linux/amd64/nodeup" (have you specified a valid file location?) will give time for this to be resolved as this beta version of kops has only come out 11 hours ago and looking into it appears the binary is not yet available at that url.

[AndrewSirenko]

FYI eksctl release v0.201.0 made metrics-server a default add-on (source)

This means that eks tests are likely failing due to a conflict between our CI scripts attempting to install metrics-server, and eksctl already doing it.

We'll either have to edit run.sh to not install metrics-server for eksctl clusters (or, less ideal, override eksctl to not install metrics-server)

[k8s-ci-robot]

@ElijahQuinones: 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-aws-ebs-csi-driver-external-test	aa4e383	link	true	/test pull-aws-ebs-csi-driver-external-test
pull-aws-ebs-csi-driver-test-helm-chart	aa4e383	link	true	/test pull-aws-ebs-csi-driver-test-helm-chart
pull-aws-ebs-csi-driver-e2e-single-az	aa4e383	link	true	/test pull-aws-ebs-csi-driver-e2e-single-az
pull-aws-ebs-csi-driver-e2e-multi-az	aa4e383	link	true	/test pull-aws-ebs-csi-driver-e2e-multi-az
pull-aws-ebs-csi-driver-external-test-arm64	aa4e383	link	false	/test pull-aws-ebs-csi-driver-external-test-arm64

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