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]: Bump CoreDNS version to 1.8.0 #96429
[kubeadm]: Bump CoreDNS version to 1.8.0 #96429
Conversation
/cc @chrisohaver |
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.
/approve
for kubeadm
@rajansandeep any notable / breaking changes in 1.8.0 that we need to add in the k/k release note?
/milestone v1.20 |
we are missing the 1.8.0 image at GCR. |
The PR to promote the CoreDNS image was merged today. kubernetes/k8s.io#1405 |
/triage accepted |
d1bda41
to
c456020
Compare
/approve |
c456020
to
b42b335
Compare
/retest |
/approve /hold is this fixing a release-blocking bug or has a feature exception been requested? if not, this should move to the 1.21 milestone. At first glance, this seems late in the cycle to be bumping an addon version |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, liggitt, neolit123, rajansandeep 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 |
Hey there, 1.20 release lead here 👋 As @LiGgit mentioned, we're pretty late in the cycle so I'm going to bump this to 1.21. Please reach out if this is release blocking and we can discuss re-milestoning back. /milestone v1.21 |
@@ -323,7 +323,7 @@ const ( | |||
CoreDNSDeploymentName = "coredns" | |||
|
|||
// CoreDNSImageName specifies the name of the image for CoreDNS add-on | |||
CoreDNSImageName = "coredns" | |||
CoreDNSImageName = "coredns/coredns" |
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 just noticed this new sub path (and v prefix)
could you please add the following second sentence in the release note:
The v1.8.0 image is now located in a "coredns" sub-path and the tag is prefixed with "v": k8s.gcr.io/coredns/coredns:v1.8.0
in case someone assumes the image is at k8s.gcr.io/coredns:1.8.0
you can /hold cancel
after that and the PR should merge.
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.
When we make custom Kind node image, it does have an assumption on k8s.gcr.io/coredns:1.8.0
,
now it breaks the basic workflow of making custom kind node image.
the question is why we are making a change on path? @rajansandeep cc @neolit123
@@ -344,7 +344,7 @@ const ( | |||
KubeDNSVersion = "1.14.13" | |||
|
|||
// CoreDNSVersion is the version of CoreDNS to be deployed if it is used | |||
CoreDNSVersion = "1.7.0" | |||
CoreDNSVersion = "v1.8.0" |
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.
just noting that if one day we want to not use a certain version of coredns with a version of k8s, we may have to introduce the same mapping / table as the one for etcd on line 448.
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.
/priority important-soon
/lgtm
we are in 1.21 , does this hold still apply or should we merge? |
/hold cancel |
/retest Review the full test history for this PR. Silence the bot with an |
Afaik there is a plan to move all images in sub paths...I do not have the
context. Also the coredns tags were missing 'v'.
kubeadm config images --kubernetes-version foo
Is a reliable source of image paths / tags for a particular version.
|
What type of PR is this?
/kind feature
What this PR does / why we need it:
Bumps the CoreDNS version to v1.8.0 in kubeadm
Also updates the corefile-migration library to v1.0.11 which supports CoreDNS v1.8.0
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: