This message was deleted.
# rke2
a
This message was deleted.
n
After spawning the cluster the agents look like this
Copy code
NAME               STATUS     ROLES                       AGE     VERSION
plane1.k8s         NotReady   control-plane,etcd,master   7m35s   v1.33.6+rke2r1
test-worker1.k8s   NotReady   <none>                      7m9s    v1.33.6+rke2r1
test-worker2.k8s   NotReady   <none>                      7m6s    v1.33.6+rke2r1
one worker2 for example is see
Copy code
test-worker2# crictl ps
CONTAINER           IMAGE               CREATED             STATE               NAME                ATTEMPT             POD ID              POD                           NAMESPACE
85e3d2742e61b       ee453f51efb81       12 minutes ago      Running             kube-proxy          0                   281ce07e5acf6       kube-proxy-test-worker2.k8s   kube-system
c
That is an ancient issue and that capacity 0 message is always printed when k3s starts for the reasons covered there
n
oh damn. Just found
Copy code
E1223 23:22:21.669524   53093 kubelet.go:3117] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
E1223 23:22:26.670511   53093 kubelet.go:3117] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
E1223 23:22:31.671799   53093 kubelet.go:3117] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
E1223 23:22:36.673015   53093 kubelet.go:3117] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
E1223 23:22:41.674478   53093 kubelet.go:3117] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
and it makes sense, i install with
cni: false
i made a fuzz about nothing.
So sorry, really. Excuse me
c
What is your actual problem
Well yes if you have no CNI the node won't be ready until you install one
That is how it works
n
For this cause, nothing. It's layer8, i just did not apply the tf project yet here and wondern. That was stupid
But generally i had a big issue with my my serverold -> server new switch over (view rke2 snapshots).
This was the reason i created this new cluster using the same network to test out things and ensure there is not firewall/network/MTU or whatever issue (and that's when i cam across this)