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, 26 Aug 2026 00:16:00 +0000 Taints: node-role.kubernetes.io/control-plane:NoSchedule node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Wed, 26 Aug 2026 00:16:24 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Wed, 26 Aug 2026 00:16:03 +0000 Wed, 26 Aug 2026 00:15:58 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Wed, 26 Aug 2026 00:16:03 +0000 Wed, 26 Aug 2026 00:15:58 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Wed, 26 Aug 2026 00:16:03 +0000 Wed, 26 Aug 2026 00:15:58 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Wed, 26 Aug 2026 00:16:03 +0000 Wed, 26 Aug 2026 00:15:58 +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.126 Hostname: instance Capacity: cpu: 8 ephemeral-storage: 78106844Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16372024Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 71983267312 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16269624Ki pods: 110 System Info: Machine ID: 6fa8155bbca44cd7a295bccc861abcd4 System UUID: 6fa8155b-bca4-4cd7-a295-bccc861abcd4 Boot ID: 6ffdcd7b-d6be-40a3-b116-0d98817975af Kernel Version: 5.15.0-190-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%) 29s kube-system kube-apiserver-instance 250m (3%) 0 (0%) 0 (0%) 0 (0%) 29s kube-system kube-controller-manager-instance 200m (2%) 0 (0%) 0 (0%) 0 (0%) 29s kube-system kube-proxy-88j8m 0 (0%) 0 (0%) 0 (0%) 0 (0%) 24s kube-system kube-scheduler-instance 100m (1%) 0 (0%) 0 (0%) 0 (0%) 29s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 32s 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 23s kube-proxy Normal Starting 37s kubelet Starting kubelet. Warning InvalidDiskCapacity 37s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 37s (x8 over 37s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 37s (x8 over 37s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 37s (x7 over 37s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 29s kubelet Starting kubelet. Warning InvalidDiskCapacity 29s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 29s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 29s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 29s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 25s node-controller Node instance event: Registered Node instance in Controller