-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Cluster API to handle kubeadm v1beta2 configuration #3150
Comments
/milestone Next Unfortunately we'll have to tackle this item in v1alpha4 given that we might need breaking changes and/or a redesign of the current APIs. |
Closing this in favor of #3150 /close |
@vincepri: Closing this issue. In response to this:
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/test-infra repository. |
It should have been closed in favor of #2769 |
User Story
As a user, I would like Cluster API to support Kubeadm v1beta2 config as part of KubeadmConfig and KubeadmControlPlane because the v1beta1 configuration is deprecated and will eventually lose support.
Detailed Description
Kubeadm is deprecated, and while there is not yet a date for removal, we should start to plan for starting to use v1beta2 in cluster API.
The issue is complicated by the fact that there is not yet agreement on k/k on how to handle component config upgrade and, as a consequence, kubeadm is not offering an automatic conversion func.
This is also relate to the work of moving kubeadm out of k/k and make it usable as a library (currently on hold 😞 ).
/kind feature
The text was updated successfully, but these errors were encountered: