Open bzub opened 7 years ago
@v1k0d3n I know the kube-router author recently made a change to the code this panic points to.
I believe it's a bug with this new code, but be sure you are using the latest kube-router docker image anyways since there's only a latest
tagged image available.
I've opened issue kube-router#23 to hopefully get that resolved.
kube-router upstream has been changed to hopefully support anything for a nodeName
with kube-router run as a pod. So you might want to docker pull
it again and try it out. I would try it out but I haven't had time to deploy any Ubuntu servers or VMs yet.
sorry took me so long to get back to this @bzub...was (and am) in the process of moving to Denver, CO. i'm on break this week and should be able to test this, and get back to you. thanks for resolving some of those issues upstream though!
No problem @v1k0d3n. I also hope to try this out soon.
By the way, I think you should try the CNI configuration with hairPinMode
set to true
. I'm still testing this out but so far it seems to fix some issues with pods talking to master components on the same host. After testing it will go into the kube-router repo officially.
So it would like:
{
"name":"kubernetes",
"type":"bridge",
"bridge":"kube-bridge",
"hairpinMode": true,
"isDefaultGateway":true,
"ipam": {
"type":"host-local"
}
}
Bringing the discussion from #3 to a proper issue.
The error with seen with kube-router is: