You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both nodes should behave the same, except for node1 having the mounts issue fixed, something i needed for a smb share extension to work.
The node without the fix command works just fine, except of course the filesystem issues that the FIX_MOUNTS was meant to fix
The node with the fix registers with the cluster, but then becomes unresponsive with [NodeStatusUnknown] Kubelet stopped posting node status. it's logs are filled with endless:
E0219 11:32:40.374545 346 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0219 11:32:40.374767 346 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0219 11:32:40.376025 346 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0219 11:32:40.376222 346 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?
E0219 11:32:43.429855 545 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0219 11:32:43.430051 545 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0219 11:32:43.431381 545 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0219 11:32:43.431559 545 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
I would expect the two to act the same. Looking through the code my only thought would be that the k3d-entrypoint.sh causes some bug with connecting to external clusters, but I am not sure where that would happen.
What did you do
How was the cluster created?
What did you do afterwards?
What did you expect to happen
Both nodes should behave the same, except for node1 having the mounts issue fixed, something i needed for a smb share extension to work.
The node without the fix command works just fine, except of course the filesystem issues that the FIX_MOUNTS was meant to fix
The node with the fix registers with the cluster, but then becomes unresponsive with
[NodeStatusUnknown] Kubelet stopped posting node status.
it's logs are filled with endless:I would expect the two to act the same. Looking through the code my only thought would be that the k3d-entrypoint.sh causes some bug with connecting to external clusters, but I am not sure where that would happen.
Screenshots or terminal output
Which OS & Architecture
Which version of
k3d
Which version of docker
The text was updated successfully, but these errors were encountered: