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: Wed, 30 Sep 2026 07:56:25 +0000 Taints: node-role.kubernetes.io/control-plane:NoSchedule node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Wed, 30 Sep 2026 07:56:49 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Wed, 30 Sep 2026 07:56:39 +0000 Wed, 30 Sep 2026 07:56:23 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Wed, 30 Sep 2026 07:56:39 +0000 Wed, 30 Sep 2026 07:56:23 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Wed, 30 Sep 2026 07:56:39 +0000 Wed, 30 Sep 2026 07:56:23 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Wed, 30 Sep 2026 07:56:39 +0000 Wed, 30 Sep 2026 07:56:23 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized Addresses: InternalIP: 162.253.55.43 Hostname: instance Capacity: cpu: 16 ephemeral-storage: 314084916Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65841444Ki pods: 110 Allocatable: cpu: 16 ephemeral-storage: 289460658107 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65739044Ki pods: 110 System Info: Machine ID: a15b6798c25142eeaafa56f70e83a791 System UUID: a15b6798-c251-42ee-aafa-56f70e83a791 Boot ID: 6565e1f4-c9ba-47c5-aa24-110ae462b70d Kernel Version: 5.15.0-194-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 (0%) 0 (0%) 100Mi (0%) 0 (0%) 21s kube-system kube-apiserver-instance 250m (1%) 0 (0%) 0 (0%) 0 (0%) 22s kube-system kube-controller-manager-instance 200m (1%) 0 (0%) 0 (0%) 0 (0%) 21s kube-system kube-proxy-vjcqj 0 (0%) 0 (0%) 0 (0%) 0 (0%) 18s kube-system kube-scheduler-instance 100m (0%) 0 (0%) 0 (0%) 0 (0%) 21s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 21s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 650m (4%) 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 16s kube-proxy Normal NodeHasSufficientMemory 29s (x8 over 29s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 29s (x8 over 29s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 29s (x7 over 29s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 22s kubelet Starting kubelet. Warning InvalidDiskCapacity 22s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 21s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 21s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 21s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 19s node-controller Node instance event: Registered Node instance in Controller