-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
kubeadm: Don't match DNS versions to K8s versions #64761
Conversation
@rosti: Reiterating the mentions to trigger a notification: 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. |
/ok-to-test |
@rajansandeep : can you review here and double check there will be no impact for CoreDNS deployment/upgrade using kubeadm ? Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm very happy about this change, it simplifies this workflow greatly. 👏
I want to check my understanding to make sure this is what I think it is: kubedns and coredns both do not depend on the k8s version. In this case 1.14.10 works for 1.9, 1.10 and 1.11 and when the version of coredns gets bumped to say, 1.15, it will work with all of the supported versions of k8s? Is this documented somewhere or are you in the core/kubeDNS community?
I want to double check this because we've had a lot of upgrade issues in the past cycle and want to make sure we don't run into more.
Thank you for this change!
kubeDNSDeploymentBytes := GetKubeDNSManifest(k8sVersion) | ||
dnsDeploymentBytes, err := kubeadmutil.ParseTemplate(kubeDNSDeploymentBytes, | ||
// v1.8.0+ has only one known YAML manifest spec for KubeDNS | ||
dnsDeploymentBytes, err := kubeadmutil.ParseTemplate(KubeDNSDeployment, | ||
struct{ ImageRepository, Arch, Version, DNSBindAddr, DNSProbeAddr, DNSDomain, MasterTaintKey string }{ | ||
ImageRepository: cfg.ImageRepository, | ||
Arch: runtime.GOARCH, | ||
// Get the kube-dns version conditionally based on the k8s version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment should be removed
This PR does not change the behavior of kubeadm in any way. It is a simple cleanup. The CoreDNS/kube-dns versions are known to work with the supported by kubeadm Kubernetes versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the update! lgtm
/lgtm |
Removed the old 1.8 comment |
/lgtm |
Fixed a couple of other comments, that were left over. |
@rosti Very good cleanup. /lgtm |
@luxas what do you think here? in or wait on 1.11? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@timothysc I think this is valuable to get into v1.11.
We had this for a reason, the manifest changed frequently for different k8s versions. Now things have settled and we're using coredns as the default which my impression is kinda stable, so now we can remove the unnecessary conditionals here IMO.
/lgtm
/approve
/milestone v1.11 |
@rosti needs rebase now though |
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process @chuckha @dixudx @luxas @rosti @timothysc Pull Request Labels
|
/retest Review the full test history for this PR. Silence the bot with an |
3 similar comments
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
/retest Review the full test history for this PR. Silence the bot with an |
Some code in kubeadm was designed with the intent, that in the future CoreDNS and kube-dns versions will match to specific K8s versions. This code is not functional, since it does not perform any version matching. As of this moment, no version matching is planned and a lot of boilerplate code is left useless. The solution is simple - remove the unneeded parts to simplify the flow. Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chuckha, dixudx, luxas, rosti The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it:
Some code in kubeadm was designed with the intent, that in the future CoreDNS
and kube-dns versions will match to specific K8s versions. This code is not
functional, since it does not perform any version matching. As of this moment,
no version matching is planned and a lot of boilerplate code is left useless.
The solution is simple - remove the unneeded parts to simplify the flow.
Signed-off-by: Rostislav M. Georgiev rostislavg@vmware.com
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes kubernetes/kubeadm#870
Special notes for your reviewer:
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews
/area kubeadm
/assign @luxas
/assign @timothysc
/kind cleanup
Release note: