-
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
Allow minikube to function with misconfigured NO_PROXY value #4229
Conversation
Can one of the admins verify this patch? |
Hi @medyagh. 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. |
unit tests to be added soon. |
@minikube-bot OK to test |
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.
It's tricky, but we should also add an integration test for proxies, something like test/integration/proxy_test.go.
To test it in a way that works for users who don't currently have a proxy, it might perhaps start one up using something like https://github.com/elazarl/goproxy
Code looks great. Just minor nits. |
Codecov Report
@@ Coverage Diff @@
## master #4229 +/- ##
==========================================
+ Coverage 32.78% 32.83% +0.05%
==========================================
Files 93 94 +1
Lines 6031 6113 +82
==========================================
+ Hits 1977 2007 +30
- Misses 3784 3835 +51
- Partials 270 271 +1
Continue to review full report at Codecov.
|
The "None" failure seems a bit strange to me, but not altogether unheard of. Go ahead and resolve the merge conflicts and we'll see if it comes up again. |
@minikube-bot OK to test |
Looks like the test is failing because it's not possible to download kubelet / kubeadm with the proxy.
Interestingly, it seems to affect more than just the proxy test:
My suggestion: check that the HTTP_PROXY environment variable isn't leaking, and ensure that all of the dependencies are downloaded by calling "minikube start --download-only" before setting up the HTTP_PROXY - or make sure that the proxy routes packets to the internet. |
@minikube-bot OK to test |
@minikube-bot OK to test |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: medyagh If they are not already assigned, you can assign the PR to them by writing 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 |
@tstromberg I wonder if that error was because the testDashboard runs in parallel. I removed the parallel to see if it works. on my machine the integration test passes for osx hyperkit |
@minikube-bot OK to test |
@minikube-bot OK test |
fixes #4130 as well as #3844