-
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
Minikube attempts to connect to internet when using http_proxy/https_proxy #5793
Comments
That is a bug ! you found ! you are right we need to mind the people in corp network ! I would be happy to review any PR that would address this. either by providing a way for people to disable the check or provide the custom DNS |
@gclawes on your corp setup, if we wanted to auto-detect the nameserver for look up how would we do it ? could you kindly provide us more info, how we could auto-detect this and use the crop provided ns? |
What's the purpose of this check? To verify that DNS resolution is working? I think the most platform independent should be able to do it in go with |
The purpose is to warn users if the VM is unable to directly connect to the internet. An app that they run in the VM won't be able to directly contact an external IP, without using a proxy server. I'd be open to improving the appearance of the check, removing it, and/or adding a flag to prevent this connection check. Thoughts? |
It looks like minikube is getting it's
|
Fixed in v1.5.2. Thank you for reporting this issue! |
restart my network adapter and its works. |
Minikube attempts to connect to the internet by running
nslookup k8s.io
against8.8.8.8
and1.1.1.1
, and pinging8.8.8.8
if those fail. In a corporate/closed network behind a proxy these DNS endpoints are not available. Minikube should use the local DNS resolvers, and possibly have a different behavior in the presence ofhttp_proxy
/HTTP_PROXY
The exact command to reproduce the issue:
minikube start
The full output of the command that failed:
The output of the
minikube logs
command:The operating system version: macOS Mojave 10.14.6
The text was updated successfully, but these errors were encountered: