-
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
virtualbox: Make DNS settings configurable #4619
Conversation
Hi @cvila84. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: cvila84 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Can one of the admins verify this patch? |
Thank you for the PR, could you tell me an example where this setting would be useful ? or how I could test this ? |
Hello @medyagh, These settings would allow people to disable the usage of Virtualbox NAT DNS proxy which can be quite unstable (see [https://www.virtualbox.org/ticket/13899?cversion=0&cnum_hist=3]). To test it, when --dns-proxy and --host-dns-resolver are set to false, the /etc/resolv.conf of the minikube VM shall contain the same DNS IP as the host. If any of the settings are true, the /etc/resolv.conf of the minikube shall be the default DNS proxy IP which is 10.2.0.3 |
ok thank you for the explain. does this have any relation with proxy or vpn ? @minikube-bot OK to test |
@medyagh i don't see any relation with proxy. the only relation i see with VPN is related to host network switching (office <-> VPN home) while minikube VM is running. when DNS proxy is deactivated, it won't reflect the new host DNS IP into /etc/resolv.conf but this is an acceptable constraint as sometimes the silent crash of Virtualbox DNS proxy prevents any communication to be done from the VM to the external world (because of DNS resolve timeout) i see the label needs-ok-to-test is still set. it seems you need to write /ok-to-test on its own line |
/retest this please |
Closes #3720
add --dns-proxy and --host-dns-resolver flags to start command for controlling virtualbox dns settings