fix: bump kubeadm config API from v1beta3 to v1beta4

[cleman95]

What this PR does

Bumps the kubeadm config template API version from v1beta3 to v1beta4.

The kubeadm.k8s.io/v1beta3 API was removed in kubeadm 1.36, causing image builds for Kubernetes 1.36+ to fail with:

error: your configuration file uses an old API spec: "kubeadm.k8s.io/v1beta3" (kind: "ClusterConfiguration").
Please use kubeadm v1.36 instead and run kubeadm config migrate

v1beta4 has been available since kubeadm 1.29, so all currently supported Kubernetes versions (1.29–1.37) accept it. The fields used in the template are unchanged between v1beta3 and v1beta4.

Which issue(s) this PR fixes

Fixes #2151
Fixes #2153

Special notes for your reviewer

This is a two-line change that only bumps the apiVersion field in the kubeadm config template. No schema changes are needed for the fields currently in use.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: cleman95 / name: Clement Phu (72f194a)

[kubernetes-prow]

[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 averagemarcus for approval. For more information see the Code Review Process.

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

Details

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

[kubernetes-prow]

Welcome @cleman95!

It looks like this is your first PR to kubernetes-sigs/image-builder 🎉. 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-sigs/image-builder 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. 😃

[kubernetes-prow]

Hi @cleman95. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

Details

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.

[drew-viles]

Duplicate of #2152

[drew-viles]

Hey @cleman95 I've been working through and looks like we already have a PR in for this. To prevent duplicates, we'll close this one and move the other forward.

[cleman95]

Sure, sorry I haven't checked if another PR was opened ! Thanks for linking the PR to my issue