-
Notifications
You must be signed in to change notification settings - Fork 2.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
Support Windows in host-gw and VXLAN modes #833
Comments
This uses new Windows Host Networking Service (HNS) features to configure networking for the host-gw mode Fixes flannel-io#833
This uses new Windows Host Networking Service (HNS) features to configure networking for the host-gw mode Fixes flannel-io#833
Hi! Are there any plans when this would be available for use on Windows K8S systems? Thanks! |
Yes we are working towards making this available... Would you like to try
early bits to see if it works for you?
…On Dec 6, 2017 1:58 AM, "Konstantin Pozdniakov" ***@***.***> wrote:
Hi!
Are there any plans when this would be available for use on Windows K8S
systems?
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#833 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADQphXAyihTEssi399tHY5veDl_Y-kkgks5s9mVXgaJpZM4PtGg_>
.
|
Count me in as a tester of early bits as well please. |
@rakelkar yes, sure! |
@cspwizard @rjmorse |
Hello @rakelkar ran kubernetes v1.9.0 cluster with flannel in VXLAN and then in host-gw mode.
started binaries
windows node sucessfully joined cluster:
created POD, which stuck in
in pod events i found that:
In kubelet windows logs was error:
This error was in VXLAN mode.
and flannel output:
and network config:
So it stuck with kubelet error After that, I've reinstalled cluster in host-gw mode
and flannel is failed to run:
and for all the next:
I appreciate any help to run it. Also, I can provide any details of my setup. Thank you. |
@kdomanski for the l2bridge issue - this is a known issue... @jroggeman made a fix for this in the underlying gonetsh library, but we didn;t update the PR (since it was closed). I need to create a new PR that includes this fix. |
For overlay - when did you build the overlay plugin? @banatm made a fix in https://github.com/rakelkar/plugins/tree/windowsCni - can you make sure you have the fix? |
For L2Bridge try #921 that should have the fix for: |
@rakelkar
If I get hns from containernetworking/plugins#85 it doesn't compile well
so where is proper location for hns? |
@rakelkar
but I have the same error:
The second run:
|
Here is how I build CNI (not a GO expert so feel free to critique my method). |
Figured out forwarding issue and crash issue.. raised pull request in underlying lib for the forwarding issue: rakelkar/gonetsh#6 |
@dmitryzykov I've updated #921 with fixes - but to use it you still need to update gonetsh (see comment on the PR) |
@madhanrm the host-gw fails for me with HNS errors that I dont understand. We've made fixes for netsh etc. to work that @dmitryzykov saw - but unable to figure out HNS errors. Can you give it a try when you get a chance? To build you need #921 but also need latest from https://github.com/rakelkar/gonetsh (to do that just delete the vendored gonetsh - and go will use the copy you cloned locally) |
@rakelkar I've tried vxlan (CNI from latest https://github.com/rakelkar/plugins/ windowsCni branch and flannel from #922 ) and I got this errors in kubelet at windows node:
kubelet at linux master node started with flanneld output:
net-conf.json
P.S. I'll test host-gw soon. |
@rakelkar I tried host-gw (CNI from latest https://github.com/rakelkar/plugins/ windowsCni branch, flannel from #921 and latest gonetsh from https://github.com/rakelkar/gonetsh) and I got this errors in kubelet at windows node:
flanneld output:
my configs:
===
===
|
Is there more up-to-date documentation for testing this? I was able to join a windows node to my cluster in VXLAN mode and even deploy a windows pod to it. The pod starts up but has no network connectivity. I can't ping the gateway, cluster DNS, or any internal / external services, but I can get pod logs and an |
@nlowe i think i have the same problem, and the kubelet logs showed that :
|
Is IP forwarding enabled on the nodes and masters? |
We are having problems with flannel on windows. Flannel leaks IPs and I am forced to cleanup the cni folder and rejoin my windows nodes. We are also getting a bunch of CNI errors about not being able to remove endpoints and finally service discovery stops working. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Windows RS3 release introduces support for Kubernetes networking, however setting it up without a Flannel like component is very difficult.The Windows Server RS3 release supports host-gw as L2Bridge and vxlan in Overlay modes - this issue proposes supporting Flannel on windows for host-gw and vxlan modes and links to a proposed PR.
See here for details on new Windows support for K8s networking: http://blog.kubernetes.io/2017/09/windows-networking-at-parity-with-linux.html
Possible Solution
Proposed PR: #832
Related CNI changes: containernetworking/plugins#76
Your Environment
The text was updated successfully, but these errors were encountered: