-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Add dnsmasq as a DNS cache in kube-dns pod #26114
Conversation
ArtfulCoder
commented
May 23, 2016
•
edited
Loading
edited
- added dns-port flag
- updated imports to not use the v1 version of the api objects.
… requests on. updated imports
LGTM. Thanks. |
Chao reviewed the import changes. |
@@ -54,13 +54,21 @@ spec: | |||
args: | |||
# command = "/kube-dns" | |||
- --domain={{ pillar['dns_domain'] }}. | |||
- --dns-port=10053 | |||
ports: | |||
- containerPort: 53 |
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.
you should update the ports info to :10053 here and duplicate this into dnsmasq on :53
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.
done.
f243dbf
to
b638913
Compare
LGTM - push your image and kick e2e |
@ArtfulCoder |
gce e2e never ran any tests and failed.. @k8s-bot test this issue: #IGNORE |
@k8s-bot test this issue: #IGNORE |
@k8s-bot test this issue: #IGNORE |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 10f9789. |
@ArtfulCoder Is dnsmasq a required container to run in order to get it working with |
Would it be better to run |