-
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
Flannel fails to watch subnet leases for other nodes in host gateway backend #83
Comments
Any fix or workaround? |
I have the same issue on windows server 2019 |
@xie-qianyue Do you think the:
message is relevant at all? I'm getting the same problem, and that seems to be the first problematic message in the logs. |
@ArchiFleKs Sorry to ping you directly, but I noticed that you also opened this issue: #96 where you say that connectivity between Linux and Windows pods was working. Does this mean you managed to figure out a workaround? |
@masaeedu no worries. I have put the windows part on hold. I have tried two setup. One with a single network card where everything was working and another with two network card on windows when depending on which card was used (one card for the external network and another one for the internal network). If I use the external network for flannel I get the lease issue and internet access but no inter pod Connectivity. And if I use the internal card, route exchange is Ok and interpod also. I get no internet in that case. My goal was to get flannel working with 2 distinct networks , one for external access, on for internal traffic. But for now I did not succeed and I have put that on standby. if I get back to it at some point I will report here. |
i have the same error. it is something wrong? |
I have the same issue as the above. hybrid cluster with a linux master, worker node and a windows node. |
Although the original post is about host-gw config it looks to be the same error (Flannel creates the network but start to communicate to the api server before things are finished) as described in: #103 (comment). The work around should be to make sure you create the External Network before starting flannel. Your There is also an open issue in flannel for the network reset: flannel-io/flannel#1272 and the route issue is in the golang sdk: kubernetes/client-go#374 |
core flannel issue flannel-io/flannel#1359; closing here /close |
@jsturtevant: 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. |
I used the latest binaries of kubernetes and the PrepareNodes script.
But I still find logs as
Failed to list *v1.Node: Get https://10.246.44.131:6443/api/v1/nodes?resourceVersion=0: http2: no cached connection was available
in flannel pod. Below is the complet log:I posted a comment here under the issue #37.
And submitted a review in #38. I have a question for the code below:
-Type Overlay
here shouldn't be-Type l2bridge
?The text was updated successfully, but these errors were encountered: