-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Feature Request] Enable host DNS resolution in virtualbox driver by default #3451
Comments
The core problem here seems to be that |
This is very close to what I'm using to demo now in Kubecon shortly, using hyperkit - I guess host resolution there works by default. HostDNS resolution in VBox: I don't see any fundamental issues with enabling it, if you'd raise a PR that would be awesome, and we can go from there. network route creation: accessing the registry from within minikube (@ceason): pull/push should be enabled with the |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
I tried to use minikube tunnel on Ubuntu 18.10 and DNS resolution of services does not work. Work only after I make this changes:
to:
$ dig +short kubernetes-dashboard.kube-system.svc.cluster.local
10.100.252.203 But after some time the process CoreDNS inside VM hangs all CPU. I found this issue maybe was related. coredns/coredns#2083 Anyone know how I can solve this? |
Since #3453 was merged - what is remaining here? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. 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. |
The default settings for the VirtualBox machine enables
DNSProxy
and disablesHostDNSResolver
. I'd like to propose reversing these settings. If the host is used for DNS resolution, we can enable the kubernetes cluster to resolve registry URLs likeregistry.kube-system.svc.cluster.local:80
, assuming that the host has properly configured acluster.local
resolver that routes traffic to the minikube network.Backstory
My local development workflow is something like this:
This allows for a rich local development experience, in which I can resolve cluster services by DNS without having to port-forward individual things (ie: http://kubernetes-dashboard.kube-system.svc.cluster.local). The problem comes when I push a new manifest to my kube installation that references containers I have pushed to my local registry. By default, since the VirtualBox host doesn't have
HostDNSResolver
enabled, it doesn't know how to resolvecluster.local
, so the image pull ends up 404'ing. If we enableHostDNSResolver
, the VB host will forward these resolution requests to my local machine, which will service them properly.This should not cause any backwards-incompatible issues (so far as I can tell) and should be a drop-in replacement for what folks are already using. I am, of course, open to putting this behind some sort of runtime configuration flag.
I've made this change in my own fork of
minikube
and it works great for my use case. I'd be happen to submit a PR.The text was updated successfully, but these errors were encountered: