Name: instance Roles: control-plane Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname=instance 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: Tue, 11 Aug 2026 07:33:25 +0000 Taints: node-role.kubernetes.io/control-plane:NoSchedule node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Tue, 11 Aug 2026 07:34:30 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Tue, 11 Aug 2026 07:33:28 +0000 Tue, 11 Aug 2026 07:33:23 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 11 Aug 2026 07:33:28 +0000 Tue, 11 Aug 2026 07:33:23 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 11 Aug 2026 07:33:28 +0000 Tue, 11 Aug 2026 07:33:23 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Tue, 11 Aug 2026 07:33:28 +0000 Tue, 11 Aug 2026 07:33:23 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Addresses: InternalIP: 199.19.213.181 Hostname: instance Capacity: cpu: 8 ephemeral-storage: 78106900Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16372032Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 71983318921 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16269632Ki pods: 110 System Info: Machine ID: de1737f2090948e4be311ecc5c8f538d System UUID: de1737f2-0909-48e4-be31-1ecc5c8f538d Boot ID: 53a36aa0-112e-4d78-af73-d138880aa4aa Kernel Version: 5.15.0-187-generic OS Image: Ubuntu 22.04.5 LTS Operating System: linux Architecture: amd64 Container Runtime Version: containerd://2.3.2 Kubelet Version: v1.28.13 Kube-Proxy Version: v1.28.13 Non-terminated Pods: (6 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- kube-system etcd-instance 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 70s kube-system kube-apiserver-instance 250m (3%) 0 (0%) 0 (0%) 0 (0%) 70s kube-system kube-controller-manager-instance 200m (2%) 0 (0%) 0 (0%) 0 (0%) 70s kube-system kube-proxy-8thp7 0 (0%) 0 (0%) 0 (0%) 0 (0%) 66s kube-system kube-scheduler-instance 100m (1%) 0 (0%) 0 (0%) 0 (0%) 71s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 70s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 650m (8%) 0 (0%) memory 100Mi (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 65s kube-proxy Normal NodeHasSufficientMemory 76s (x8 over 76s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 76s (x8 over 76s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 76s (x7 over 76s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 70s kubelet Starting kubelet. Warning InvalidDiskCapacity 70s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 70s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 70s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 70s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 67s node-controller Node instance event: Registered Node instance in Controller