This message was deleted.
# k3sa
adamant-kite-43734
12/08/2022, 6:17 PMThis message was deleted.
c
creamy-pencil-82913
12/08/2022, 6:20 PMYou might put that giant wall of text in a thread next time
creamy-pencil-82913
12/08/2022, 6:20 PMcontainer runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initializedDid you disable flannel?
creamy-pencil-82913
12/08/2022, 6:20 PMAre you missing vxlan support in your kernel?
a
aloof-dusk-52700
12/08/2022, 6:22 PMsorry about that the giant wall of text
aloof-dusk-52700
12/08/2022, 6:22 PMNo i didnt disable flannel. not sure what that is
aloof-dusk-52700
12/08/2022, 6:31 PMI should note that the node status was ready until I tried to add a worker node onto the cluster
c
creamy-pencil-82913
12/08/2022, 6:38 PMI don’t see the other node in the cluster
creamy-pencil-82913
12/08/2022, 6:38 PMDo they both have the same hostname or something?
creamy-pencil-82913
12/08/2022, 6:38 PMor are you trying to run k3s twice on the same node?
creamy-pencil-82913
12/08/2022, 6:38 PMwhat do the k3s service logs say on that node?
a
aloof-dusk-52700
12/08/2022, 6:40 PMNo, I have two Pynq and they have different hostnames. But I had turned off one of the devices.
aloof-dusk-52700
12/08/2022, 7:46 PMI realized I was using the wrong IP address for my master and thats why I was not seeing the worker node.
Not sure if thats the reason why I was having the notready state. However I changed the IP address and now I see both the master and worker node present and status is ready
aloof-dusk-52700
12/08/2022, 7:46 PMThank you for your help
56 Views