-
Notifications
You must be signed in to change notification settings - Fork 39.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: Pull sidecar and dnsmasq-nanny images when using kube-dns #66499
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. |
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews |
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.
/lgtm
/approve
/hold
Please make sure this is working with appropriate unit tests. If we don't already have tests covering all of this, write them as part of this patch.
I'm missing something, why is this needed, and can you cross link the canonical reference from folks who manage these integrations. /cc @MrHohn Are you aware of this requirement, and where did it come from? |
I was a bit baffled by this too, but it is true. Tried it with a clean setup in a VM with Kubernetes 1.11.1 and it indeed fetched the sidecar and dnsmasq-nanny images and started them up:
|
It appears that sidecar and dnsmasq-nanny images are now required for kube-dns deployment to work correctly. Thus the following default kube-dns images are used now: - k8s.gcr.io/k8s-dns-kube-dns-amd64:1.14.10 - k8s.gcr.io/k8s-dns-sidecar-amd64:1.14.10 - k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64:1.14.10 Signed-off-by: Rostislav M. Georgiev <[email protected]>
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.
/lgtm
/approve
Thanks!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
/hold cancel |
Humm sorry I'm missing some context here. From kube-dns point of view these two images are always required since long ago (1.5ish?). This feels like some sort of pre-loading mechanism in kubeadm, does it work on earlier k8s versions? |
Automatic merge from submit-queue (batch tested with PRs 66291, 66471, 66499). If you want to cherry-pick this change to another branch, please follow the instructions here. |
@rosti we might wanna cherrypick this bugfix into v1.11 |
i will cherry pick it tomorrow. |
What this PR does / why we need it:
It appears that sidecar and dnsmasq-nanny images are now required for
kube-dns deployment to work correctly. Thus the following default kube-dns
images are used now:
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#1016
Special notes for your reviewer:
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews
/area kubeadm
/assign @luxas
/assign @timothysc
/kind bug
Release note: