hello I have been trying to install k3s on a xilinx board PYNQ Z1 and I keep getting status notready when I run Kubectl get nodes below is the output Can someone help me I am new to kubernetes root pynq home xilinx kubectl get nodes NAME STATUS ROLES AGE VERSION pynq NotReady control plane master 8d v1 25 4+k3s1 root pynq home xilinx kubectl describe node pynq Name pynq Roles control plane master Labels <http beta kubernetes io arch=arm|beta kubernetes io arch=arm> <http beta kubernetes io instance type=k3s|beta kubernetes io instance type=k3s> <http beta kubernetes io os=linux|beta kubernetes io os=linux> <http egress k3s io cluster=true|egress k3s io cluster=true> <http kubernetes io arch=arm|kubernetes io arch=arm> <http kubernetes io hostname=pynq|kubernetes io hostname=pynq> <http kubernetes io os=linux|kubernetes io os=linux> <http node role kubernetes io control plane=true|node role kubernetes io control plane=true> <http node role kubernetes io master=true|node role kubernetes io master=true> <http node kubernetes io instance type=k3s|node kubernetes io instance type=k3s> Annotations <http flannel alpha coreos com backend data|flannel alpha coreos com backend data> VNI 1 VtepMAC 86 e8 b1 26 60 bc <http flannel alpha coreos com backend type|flannel alpha coreos com backend type> vxlan <http flannel alpha coreos com kube subnet manager|flannel alpha coreos com kube subnet manager> true <http flannel alpha coreos com public ip|flannel alpha coreos com public ip> 192 168 0 115 <http k3s io hostname|k3s io hostname> pynq <http k3s io internal ip|k3s io internal ip> 192 168 0 115 <http k3s io node args|k3s io node args> server flannel backend none <http k3s io node config hash|k3s io node config hash> 447SKVE725DJE7IL6YFZKSK35XQASDGUESLF6EHAW2PGVRUPL5OQ==== <http k3s io node env|k3s io node env> K3S DATA DIR var lib rancher k3s data bf78b680b175415f467303cca6d37bb8d7eac8bf0b6bd0a65a72cc26d01efbdb K3S KUBECONFIG MODE 644 <http node alpha kubernetes io ttl|node alpha kubernetes io ttl> 0 <http volumes kubernetes io controller managed attach detach|volumes kubernetes io controller managed attach detach> true CreationTimestamp Wed 30 Nov 2022 08 23 56 +0000 Taints <http node kubernetes io not ready NoSchedule|node kubernetes io not ready NoSchedule> Unschedulable false Lease HolderIdentity pynq AcquireTime lt unset gt RenewTime Thu 08 Dec 2022 18 12 57 +0000 Conditions Type Status LastHeartbeatTime LastTransitionTime Reason Message MemoryPressure False Thu 08 Dec 2022 18 09 34 +0000 Wed 30 Nov 2022 08 34 42 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Thu 08 Dec 2022 18 09 34 +0000 Wed 30 Nov 2022 08 34 42 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Thu 08 Dec 2022 18 09 34 +0000 Wed 30 Nov 2022 08 34 42 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Thu 08 Dec 2022 18 09 34 +0000 Thu 01 Dec 2022 06 23 39 +0000 KubeletNotReady container runtime network not ready NetworkReady=false reason NetworkPluginNotReady message Network plugin returns error cni plugin not initialized Addresses InternalIP 192 168 0 115 Hostname pynq Capacity cpu 2 ephemeral storage 15089632Ki memory 505428Ki pods 110 Allocatable cpu 2 ephemeral storage 14679193999 memory 505428Ki pods 110 System Info Machine ID 5a5ef3f8a3034b4c8b00d42b6daec8fb System UUID 5a5ef3f8a3034b4c8b00d42b6daec8fb Boot ID 63304d8c 9a1e 4d60 9f29 105755b27543 Kernel Version 5 15 19 xilinx v2022 1 OS Image PynqLinux based on Ubuntu 22 04 Operating System linux Architecture arm Container Runtime Version <containerd 1 6 8 k3s1> Kubelet Version v1 25 4+k3s1 Kube Proxy Version v1 25 4+k3s1 PodCIDR 10 42 0 0 24 PodCIDRs 10 42 0 0 24 ProviderID <k3s pynq> Non terminated Pods 5 in total Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age kube system helm install traefik 6l4hc 0 0 0 0 0 0 0 0 8d kube system helm install traefik crd lbmbv 0 0 0 0 0 0 0 0 8d kube system local path provisioner 79f67d76f8 rbtxb 0 0 0 0 0 0 0 0 8d kube system metrics server 5c8978b444 9z4dk 100m 5 0 0 70Mi 14 0 0 8d kube system coredns 597584b69b 2sd6j 100m 5 0 0 70Mi 14 170Mi 34 8d Allocated resources Total limits may be over 100 percent i e overcommitted Resource Requests Limits cpu 200m 10 0 0 memory 140Mi 28 170Mi 34 ephemeral storage 0 0 0 0 Events lt none gt

hello I have been trying to install k3s on a xilinx board PY rancher-users #k3s

Title

aloof-dusk-52700

12/08/2022, 6:17 PM

hello I have been trying to install k3s on a xilinx board PYNQ Z1 and I keep getting status notready when I run Kubectl get nodes. below is the output. Can someone help me? I am new to kubernetes root@pynq:/home/xilinx# kubectl get nodes NAME STATUS ROLES AGE VERSION pynq NotReady control-plane,master 8d v1.25.4+k3s1 root@pynq:/home/xilinx# kubectl describe node pynq Name: pynq Roles: control-plane,master Labels: beta.kubernetes.io/arch=arm beta.kubernetes.io/instance-type=k3s beta.kubernetes.io/os=linux egress.k3s.io/cluster=true kubernetes.io/arch=arm kubernetes.io/hostname=pynq kubernetes.io/os=linux node-role.kubernetes.io/control-plane=true node-role.kubernetes.io/master=true node.kubernetes.io/instance-type=k3s Annotations: flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"86:e8:b1:26:60:bc"} flannel.alpha.coreos.com/backend-type: vxlan flannel.alpha.coreos.com/kube-subnet-manager: true flannel.alpha.coreos.com/public-ip: 192.168.0.115 k3s.io/hostname: pynq k3s.io/internal-ip: 192.168.0.115 k3s.io/node-args: ["server","--flannel-backend","none"] k3s.io/node-config-hash: 447SKVE725DJE7IL6YFZKSK35XQASDGUESLF6EHAW2PGVRUPL5OQ==== k3s.io/node-env: {"K3S_DATA_DIR":"/var/lib/rancher/k3s/data/bf78b680b175415f467303cca6d37bb8d7eac8bf0b6bd0a65a72cc26d01efbdb","K3S_KUBECONFIG_MODE":"644"} node.alpha.kubernetes.io/ttl: 0 volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp: Wed, 30 Nov 2022 08:23:56 +0000 Taints: node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: pynq AcquireTime: <unset> RenewTime: Thu, 08 Dec 2022 18:12:57 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Thu, 08 Dec 2022 18:09:34 +0000 Wed, 30 Nov 2022 08:34:42 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Thu, 08 Dec 2022 18:09:34 +0000 Wed, 30 Nov 2022 08:34:42 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Thu, 08 Dec 2022 18:09:34 +0000 Wed, 30 Nov 2022 08:34:42 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Thu, 08 Dec 2022 18:09:34 +0000 Thu, 01 Dec 2022 06:23:39 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Addresses: InternalIP: 192.168.0.115 Hostname: pynq Capacity: cpu: 2 ephemeral-storage: 15089632Ki memory: 505428Ki pods: 110 Allocatable: cpu: 2 ephemeral-storage: 14679193999 memory: 505428Ki pods: 110 System Info: Machine ID: 5a5ef3f8a3034b4c8b00d42b6daec8fb System UUID: 5a5ef3f8a3034b4c8b00d42b6daec8fb Boot ID: 63304d8c-9a1e-4d60-9f29-105755b27543 Kernel Version: 5.15.19-xilinx-v2022.1 OS Image: PynqLinux, based on Ubuntu 22.04 Operating System: linux Architecture: arm Container Runtime Version: containerd://1.6.8-k3s1 Kubelet Version: v1.25.4+k3s1 Kube-Proxy Version: v1.25.4+k3s1 PodCIDR: 10.42.0.0/24 PodCIDRs: 10.42.0.0/24 ProviderID: k3s://pynq Non-terminated Pods: (5 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- kube-system helm-install-traefik-6l4hc 0 (0%) 0 (0%) 0 (0%) 0 (0%) 8d kube-system helm-install-traefik-crd-lbmbv 0 (0%) 0 (0%) 0 (0%) 0 (0%) 8d kube-system local-path-provisioner-79f67d76f8-rbtxb 0 (0%) 0 (0%) 0 (0%) 0 (0%) 8d kube-system metrics-server-5c8978b444-9z4dk 100m (5%) 0 (0%) 70Mi (14%) 0 (0%) 8d kube-system coredns-597584b69b-2sd6j 100m (5%) 0 (0%) 70Mi (14%) 170Mi (34%) 8d Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 200m (10%) 0 (0%) memory 140Mi (28%) 170Mi (34%) ephemeral-storage 0 (0%) 0 (0%) Events: <none>

creamy-pencil-82913

12/08/2022, 6:20 PM

You might put that giant wall of text in a thread next time

container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

Did you disable flannel?

Are you missing vxlan support in your kernel?

aloof-dusk-52700

12/08/2022, 6:22 PM

sorry about that the giant wall of text

No i didnt disable flannel. not sure what that is

I should note that the node status was ready until I tried to add a worker node onto the cluster

creamy-pencil-82913

12/08/2022, 6:38 PM

I don’t see the other node in the cluster

Do they both have the same hostname or something?

or are you trying to run k3s twice on the same node?

what do the k3s service logs say on that node?

aloof-dusk-52700

12/08/2022, 6:40 PM

No, I have two Pynq and they have different hostnames. But I had turned off one of the devices.

I 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

Thank you for your help

19 Views

#k3s Join Slack