Implement support for kubeadm v1beta4 API

[fabriziopandini]

What would you like to be added (User Story)?

As a user, I want to be able to create clusters with kubeadm 1.31 (which most probably is going to use v1beta4 API)
As a user, I want to be able to use latest and greatest introduced by kubeadm v1beta4 API

rif kubernetes/kubernetes#125029

Action Plan

Mandatory tasks to support Kubernetes v1.31:

• Implements conversions from CAPI v1beta1 types to kubeadm v1beta4 ✨ Add kubeadm v1beta4 types #10709
  • Special handling should be implemented for ClusterConfiguration.TimeoutForControlPlane and JoinConfiguration.Discovery.Timeout

Optional non breaking changes to be implemented ASAP:

•  Before adding new fields, check potential impacts on things like

  cluster-api/controlplane/kubeadm/internal/filters.go

  Line 220 in 57dc231

  match, diff, err := compare.Diff(machineClusterConfig, kcpLocalClusterConfiguration)

  , also ClusterClass and topology reconcile ✨ Add ExtraEnvs and ImagePullSerial to KubeadmConfig #10846
• Add ClusterConfiguration.*.ExtraEnvs ✨ Add ExtraEnvs and ImagePullSerial to KubeadmConfig #10846
• Add Init/JoinConfiguration.NodeRegistrationOptions.ImagePullSerial ✨ Add ExtraEnvs and ImagePullSerial to KubeadmConfig #10846
• Add Init/JoinConfiguration.Timeout: ⚠️ Align KubeadmConfig to kubeadm v1beta4 types #12282
  • Important: Timeout.ControlPlaneComponentHealthCheck and Timeout.TLSBootstrap must not be added now to ensure a clean migration of ClusterConfiguration.TimeoutForControlPlane and JoinConfiguration.Discovery.Timeout when we introduce CAPI v1beta2 types

Changes deferred to when we implemening CAPI v1beta2 types

• Refactor ClusterConfiguration.*.ExtraArgs and Init/JoinConfiguration.NodeRegistrationOptions.KubeletExtraArgs ⚠️ Align KubeadmConfig to kubeadm v1beta4 types #12282
• Add Timeout.ControlPlaneComponentHealthCheck and Timeout.TLSBootstrap and remove ClusterConfiguration.TimeoutForControlPlane and JoinConfiguration.Discovery.Timeout ⚠️ Align KubeadmConfig to kubeadm v1beta4 types #12282
• change type for ImagePullPolicy ⚠️ Align KubeadmConfig to kubeadm v1beta4 types #12282

Changes deferred to when we review certificate management / renewal --> #12289

Changes deferred to when we review kubeadm/KCP addon management --> #12288

Changes deferred to when we implement EncryptionAlgorithm for certificates -> #10077

Label(s) to be applied

/kind feature

[fabriziopandini]

/priority important-soon
note: priority assumes we can continue to work with v1beta3 API, but if this is not true it must be bumped to critical-urgent

[sbueringer]

/reopen

[k8s-ci-robot]

@sbueringer: Reopened this issue.

In response to this:

/reopen

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.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[sbueringer]

/lifecycle frozen

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues 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 issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[superbrothers]

Add Init/JoinConfiguration.Timeout

Is it possible to work on the above task now?

Our cluster has a large etcd db, which causes the learner to fail to promote to follower, so we have disabled kubeadm EtcdLearnerMode. However, this option was removed in v1.33 with GA. Therefore, we would like to use timeouts.etcdAPICall.

• https://github.com/kubernetes/kubernetes/blob/v1.32.5/cmd/kubeadm/app/util/etcd/etcd.go#L574

[sbueringer]

@fabriziopandini is just now taking a closer look at this issue and at least implement some part of it. (I let him respond if what you are asking for is covered there or not)

[fabriziopandini]

#12282 implements changes for extra args, timeouts and image pull polices

Other changes with broader impacts on other CAPI features are tracked in separated issues:

Certificate management / renewal --> #12289

Proxy and DNS installation and management --> #12288

Support more EncryptionAlgorithm for certificates -> #10077