Update all the kubernetes versions to 1.32

[jsturtevant]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
1.29 is EOL, this updates all reference to keep things fresh.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

TODOs:

• squashed commits
• includes documentation
• adds unit tests
• cherry-pick candidate

Release note:

Update default Kubernetes version to 1.32

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.26%. Comparing base (1a9b38b) to head (cfc3978).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5528   +/-   ##
=======================================
  Coverage   53.26%   53.26%           
=======================================
  Files         272      272           
  Lines       29529    29529           
=======================================
  Hits        15730    15730           
  Misses      12984    12984           
  Partials      815      815           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jsturtevant]

@mboersma are we still building flatcar images?

 <*exported.ResponseError | 0xc000c524e0>: 
      GET https://management.azure.com/subscriptions/46678f10-4bbb-447e-98e8-d2829589f2d8/providers/Microsoft.Compute/locations/uksouth/communityGalleries/flatcar4capi-742ef0cb-dcaa-4ecb-9cb0-bfd2e43dccc0/images/flatcar-stable-amd64-capi-stable-1.32/versions
      --------------------------------------------------------------------------------
      RESPONSE 404: 404 Not Found
      ERROR CODE: NotFound

[mboersma]

are we still building flatcar images?

The CAPZ team never did build them, but the Flatcar team was building them in a community gallery. But AFAICT they stopped publishing a while back, once they got their preferred sysext approach working.

[jsturtevant]

are we still building flatcar images?

The CAPZ team never did build them, but the Flatcar team was building them in a community gallery. But AFAICT they stopped publishing a while back, once they got their preferred sysext approach working.

I can revert the changes to these versions but should these tests be dropped if they aren't maintained?

[jsturtevant]

/retest

[jsturtevant]

/test pull-cluster-api-provider-azure-apiversion-upgrade

[jsturtevant]

/retest

[jsturtevant]

I am seeing the same panic in the cloudprovider image: #5523 (comment)

It seem that test is buggy

/retest

[jsturtevant]

/retest

[mboersma]

should these tests be dropped if they aren't maintained?

Yes, probably. We could ask the Flatcar team for their opinions--I know they prefer sysext to baking full node images.

[jsturtevant]

failure looks like a flake on the azure cni test
/test pull-cluster-api-provider-azure-e2e

[jsturtevant]

/retest

[nawazkh]

/retest

[nawazkh]

Is the recent run of the test a flake ? Let's retest
/test pull-cluster-api-provider-azure-e2e-workload-upgrade

[willie-yao]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 0d53edd01c193fdc857bfc894fcae4bdefcb0f83

[nawazkh]

/test pull-cluster-api-provider-azure-e2e-workload-upgrade

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[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 willie-yao. 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

[willie-yao]

/retest

[jsturtevant]

/test pull-cluster-api-provider-azure-apiversion-upgrade

[jsturtevant]

/retest

[willie-yao]

/retest

[k8s-ci-robot]

@jsturtevant: 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-cluster-api-provider-azure-conformance	8c10b38	link	false	/test pull-cluster-api-provider-azure-conformance
pull-cluster-api-provider-azure-conformance-ipv6-with-ci-artifacts	8c10b38	link	false	/test pull-cluster-api-provider-azure-conformance-ipv6-with-ci-artifacts
pull-cluster-api-provider-azure-conformance-custom-builds	8c10b38	link	false	/test pull-cluster-api-provider-azure-conformance-custom-builds
pull-cluster-api-provider-azure-apiversion-upgrade	cfc3978	link	true	/test pull-cluster-api-provider-azure-apiversion-upgrade
pull-cluster-api-provider-azure-e2e	cfc3978	link	true	/test pull-cluster-api-provider-azure-e2e

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.