Implement support for kubeadm v1beta4 API #10708
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
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
Detailed Description
Changes introduced by kubeadm v1beta4 that we might add to CABPK without breaking changes (caveats, those changes apply only to clusters with K8s >= 1.31, for older cluster they are no-op)
Changes introduced by kubeadm v1beta4 that require CABPK breaking changes to be implemented
Changes introduced by kubeadm v1beta4 that are not relevant to CABPK
Anything else you would like to add?
rif kubernetes/kubernetes#125029
Action Plan
Mandatory tasks to support Kubernetes v1.31:
Optional non breaking changes to be implemented ASAP:
cluster-api/controlplane/kubeadm/internal/filters.go
Line 220 in 57dc231
Changes deferred to when we review certificate management / renewal
Changes deferred to when we review kubeadm/KCP addon management
Changes deferred to when we implement #10077
Changes deferred to when we implement CAPI v1beta2 types
Label(s) to be applied
/kind feature
The text was updated successfully, but these errors were encountered: