-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix NO_PROXY #1573
fix NO_PROXY #1573
Conversation
BenTheElder
commented
May 8, 2020
- inspect the correct docker network
- include node names in no_proxy
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder 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 |
@@ -271,18 +283,20 @@ func runArgsForLoadBalancer(cfg *config.Cluster, name string, args []string) ([] | |||
return append(args, loadbalancer.Image), nil | |||
} | |||
|
|||
func getProxyEnv(cfg *config.Cluster) (map[string]string, error) { | |||
func getProxyEnv(cfg *config.Cluster, networkName string, nodeNames []string) (map[string]string, error) { |
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.
should []nodeNames
be in common
and not provider specific?
nah, 💤 , too late for this 🙃
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.
nah, there's no DNS in the others at the moment. we can DRY out later if that becomes the case
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.
/lgtm
@BenTheElder: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
hrm NFS flakes ... https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kind/1573/pull-kind-e2e-kubernetes/1258906611737432064 going to need to devote some time to test deflake very soon. |
Is my understanding right that in kind v0.8.x until this commit is included, or in kind v0.8.0 and v0.8.1, users need to specify The document asks to add "172.17.0.0/16" to I've tested with v0.8.1, v0.8.0, v0.7.0, and master branch and reached to above conclusion, which took me a bit of time. If above is correct, I think that it is worth documented in somewhere. (If next version is planed to release soon, there won't be many people confused by this, though.) BTW, this PR is very nice work, for it removed much complexity for users in deploying kind behind a proxy. Thank you very much for your work! |
That's correct, sorry about that. The next release is tentatively due by june 1st, though we got a bit less done than I hoped so far .. https://github.com/kubernetes-sigs/kind/milestones
thanks :-) |