-
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
Document removal of kube-dns support in kubeadm #4026
Comments
/remove-kind feature /milestone v0.4.0 |
@fabriziopandini hi! Has someone started working on this? I am happy to help if no one is interested. (Suggestions/pointers where to start looking and where notes must be put would be awesome to have). |
/good-first-issue |
@vincepri: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed 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. |
@fabriziopandini Hi, I am a new contributor, would like to work on this. Would appreciate your suggestions/pointers. |
/assign @sgirem463 |
What about adding a note in https://cluster-api.sigs.k8s.io/tasks/kubeadm-control-plane.html#kubeconfig-management. Something like
|
@fabriziopandini I will work on this |
@fabriziopandini @vincepri ALLANs-MBP:tasks alue$ Using the Kubeadm control plane type to manage a control plane provides several ways to upgrade control plane machines. + + + Warning+ +KCP support only CoreDNS as a DNS server; also kube-dns support has been removed by kubeadm in v1.21. + + + Kubeconfig managementKCP will generate and manage the admin Kubeconfig for clusters. The client certificate for the admin user is created I am not sure what tests should be done for document updates. Is there anything else I should do before pulling a PR? |
@sgirem463 I think it's totally fine to just open a PR to propose this change. |
…ubernetes-sigs#4026' minor update to correct a spelling issue changed to: KubeadmControlPlane is solely supporting CoreDNS as a DNS server at this time.
Kubeadm is going to drop support for kube-dns in version 1.21 (xref kubernetes/kubeadm#1943).
This should not be a problem for CABPK/KCP users, given that almost all of them should be using CoreDNS, however, we should consider if/how to issue a note to our user in case someone is still using kube-dns by twicking KubeadmConfig.Cluster configuration.
/kind feature
The text was updated successfully, but these errors were encountered: