Get rid of userspace proxying #330
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Another attempt to solve #43 for everyone. |
Determine the master IP via ssh over eth1. This allows nodes to find out the IP of eth0 of the master. Signed-off-by: Roman Mohr <rmohr@redhat.com>
|
Deployment and functional tests work for me. |
|
We also have a confirmation from @cynepco3hahue that this fixes his setup. |
fabiand
approved these changes
Jul 20, 2017
mzzgaopeng
pushed a commit
to mzzgaopeng/kubevirt
that referenced
this pull request
Mar 8, 2021
Expand description of goroutine+netns problems
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Determine the master IP via ssh over eth1. This allows nodes to find out
the IP of eth0 of the master.
Background is, that DNS probes from nodes to resolve the master IP, in some libvirt/vagrant combinations point to wrong IPs. Therefore, use the well known IP of eth1, to connect to the master, and get the IP of eth0 from the master directly. This allows kubeadm on the node, to use the right IP to connect to the master. If we don't do that, we have to mess around with Kubernetes and the netork providers, to use eth1, which is error prone, and some people are still seeing deployment issues.