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/dns/coredns to 1.8.0 as kubeadm #99752
Conversation
@pacoxu: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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's expected that kube-up and kubeadm are both updated for better coverage in CI |
@BenTheElder I updated the coredns-kube-up part. kubeadm has already used 1.8.0. for new released 1.8.3, I may work on the corefile-migration first. |
Hi @pacoxu, thank you for picking this up. |
@rajansandeep Updated. Is there any update for the corefile? |
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
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, MrHohn, pacoxu 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
#96429 use 1.8.0 in kubeadm of 1.21
So I think we should upgrade the coredns image here as well.
Which issue(s) this PR fixes:
part of #99751
Special notes for your reviewer:
Does this PR introduce a user-facing change?