Open fabriziopandini opened 4 months ago
This issue is currently awaiting triage.
If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/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
/reopen
@sbueringer: Reopened this issue.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
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 https://github.com/kubernetes/kubernetes/pull/125029
Action Plan
Mandatory tasks to support Kubernetes v1.31:
Optional non breaking changes to be implemented ASAP:
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 https://github.com/kubernetes-sigs/cluster-api/issues/10077
Changes deferred to when we implement CAPI v1beta2 types
Label(s) to be applied
/kind feature