Name: controller-1 Roles: control-plane Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname=controller-1 kubernetes.io/os=linux node-role.kubernetes.io/control-plane= node.kubernetes.io/exclude-from-external-load-balancers= Annotations: kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl: 0 volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp: Sat, 18 Apr 2026 17:53:00 +0000 Taints: node.cilium.io/agent-not-ready:NoSchedule node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: controller-1 AcquireTime: RenewTime: Sat, 18 Apr 2026 17:56:49 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Sat, 18 Apr 2026 17:56:44 +0000 Sat, 18 Apr 2026 17:52:59 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Sat, 18 Apr 2026 17:56:44 +0000 Sat, 18 Apr 2026 17:52:59 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Sat, 18 Apr 2026 17:56:44 +0000 Sat, 18 Apr 2026 17:52:59 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Sat, 18 Apr 2026 17:56:44 +0000 Sat, 18 Apr 2026 17:52:59 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Addresses: InternalIP: 199.204.45.19 Hostname: controller-1 Capacity: cpu: 8 ephemeral-storage: 78147108Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16382192Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 72020374614 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16279792Ki pods: 110 System Info: Machine ID: 58b3f78badf54cd7b386b1c3455ae039 System UUID: 58b3f78b-adf5-4cd7-b386-b1c3455ae039 Boot ID: 7ca2dbf0-baa4-4f60-a8fb-5542951c8bc5 Kernel Version: 6.12.74+deb13+1-amd64 OS Image: Debian GNU/Linux 13 (trixie) Operating System: linux Architecture: amd64 Container Runtime Version: containerd://2.2.2 Kubelet Version: v1.33.4 Kube-Proxy Version: Non-terminated Pods: (7 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- kube-system cilium-6bdrq 100m (1%) 0 (0%) 10Mi (0%) 0 (0%) 45s kube-system etcd-controller-1 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 3m46s kube-system kube-apiserver-controller-1 250m (3%) 0 (0%) 0 (0%) 0 (0%) 3m45s kube-system kube-controller-manager-controller-1 200m (2%) 0 (0%) 0 (0%) 0 (0%) 3m45s kube-system kube-proxy-lq49r 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m40s kube-system kube-scheduler-controller-1 100m (1%) 0 (0%) 0 (0%) 0 (0%) 3m51s kube-system kube-vip-controller-1 0 (0%) 0 (0%) 0 (0%) 0 (0%) 3m52s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 750m (9%) 0 (0%) memory 110Mi (0%) 0 (0%) ephemeral-storage 0 (0%) 0 (0%) hugepages-1Gi 0 (0%) 0 (0%) hugepages-2Mi 0 (0%) 0 (0%) Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Starting 3m37s kube-proxy Normal Starting 3m56s kubelet Starting kubelet. Warning InvalidDiskCapacity 3m56s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 3m56s (x8 over 3m56s) kubelet Node controller-1 status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 3m56s (x8 over 3m56s) kubelet Node controller-1 status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 3m56s (x8 over 3m56s) kubelet Node controller-1 status is now: NodeHasSufficientPID Normal Starting 3m42s kubelet Starting kubelet. Warning InvalidDiskCapacity 3m42s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 3m42s kubelet Node controller-1 status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 3m42s kubelet Node controller-1 status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 3m42s kubelet Node controller-1 status is now: NodeHasSufficientPID Normal RegisteredNode 3m40s node-controller Node controller-1 event: Registered Node controller-1 in Controller