-
Notifications
You must be signed in to change notification settings - Fork 123
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
vxlan keeps failing when trying to join network #40
Comments
I gave it an extra shot today, and a search somehow got me to this issue on flannel: flannel-io/flannel#1178 It seems to me, that the reason for my errors is a result of everything going so fast, that documentation is not kept up to date. For instance, in the lastest kube-flannel.yaml, name is cbr0. Changing this be simply re-applying kube-flannel does in fact change the masters /etc/cni/net.d/10-flannel.conflist. You really need to keep an eye out for these small tweaks. For now it seems i can join - and unlike my two previous attempts (host-gw and vxlan) it also looks like I have connectivity from the POD. A small hooray for now. Hope this can help someone struggling the win-worker challenge ;-) |
There is most defiantly a bug somewhere .. sometime it takes 5+ retries to do the -install, -join and -reset (repeat), before the node is actually joined. Getting tired - just wanted to keep you posted .. |
I really don't know what is up and down .. sometime it works .. sometime not .. sometime some of the nodes .. sometimes others .. Here is an error from one of the nodes:
|
After a restart of the 3 worker nodes:
|
As part of the move to the new kubeadm on Windows approach with 1.18 we are closing issues related to the previous alpha. |
@benmoss: Closing this issue. In response to this:
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. |
Sounds good; I am actually pursuing this now - however, my deamonsets are not working and the latest 0.12.0r2 Flannel image is raising errors. Do you have some reading material to follow? Currently I am running 1.17.3. Thanks. |
Thank you for the link; i can see I worked most things out yesterday by browsing this tool. That said, even following the new documentation, I am experiencing errors from both DeamonSet. I will, until guided otherwise, provide the error information here (hopefully it can help you guys out): FLANNEL (sigwindowstools/flannel:0.12.0-rc2)
KUBEPROXY (sigwindowstools/kube-proxy:v1.17.3)
The error from kube-proxy make sense, given that Flannel is not setup .. i am guessing that Flannel is also providing the HNS network? Thanks. |
Are you running wins? You can't just run the DaemonSets without wins as well. |
Basically I followed the document and started with the preparenode PowerShell. It looks like it is doing some wins setup using rancher. Anything I overlooked? |
Hmm, I don't know what file it would be talking about then. I thought it was the HostPath volume mount. |
So, after a whole weekend of trial and error with the "official" guide from Microsoft (https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/network-topologies) I decided (more or less by coincidence) to give this a try (refereed from https://kubernetes.io/docs/setup/production-environment/windows/user-guide-windows-nodes/).
After my third re-install (which should have been the charm) i keep being blocked by a network issue.
It is running on a hypervisor having the en_windows_server_version_1909_updated_feb_2020_x64_dvd_8c906407.iso (Windows Server Version 1909) and an Intel NUC I7.
So, after the install, which followed this modified script:
Everything supposedly goes fine until the flanneld is firing up:
And the kubelet gives these errors:
I have disabled the firewall completely.
Linux is working perfectly.
Here is a kubectl get pods -n=kube-system
Here is the kube-flannel.yaml
Any help is greatly appreciated.
When I do a kubectl get nodes, it is listing the win worker .. but given the errors listed above, i have no hope that it is working.
So until i hear from a smart person, I have applied the -reset to the scripts.
Thanks.
The text was updated successfully, but these errors were encountered: