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:03 +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:26 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Wed, 26 Aug 2026 00:16:06 +0000 Wed, 26 Aug 2026 00:16:00 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Wed, 26 Aug 2026 00:16:06 +0000 Wed, 26 Aug 2026 00:16:00 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Wed, 26 Aug 2026 00:16:06 +0000 Wed, 26 Aug 2026 00:16:00 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Wed, 26 Aug 2026 00:16:06 +0000 Wed, 26 Aug 2026 00:16:00 +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.208 Hostname: instance Capacity: cpu: 8 ephemeral-storage: 78106844Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16372028Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 71983267312 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16269628Ki pods: 110 System Info: Machine ID: f4e1c85d58e94148b645a5e3b7b687c6 System UUID: f4e1c85d-58e9-4148-b645-a5e3b7b687c6 Boot ID: a38d6b87-467f-4085-8373-203e08b67ad6 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%) 26s kube-system kube-apiserver-instance 250m (3%) 0 (0%) 0 (0%) 0 (0%) 26s kube-system kube-controller-manager-instance 200m (2%) 0 (0%) 0 (0%) 0 (0%) 26s kube-system kube-proxy-x2tj6 0 (0%) 0 (0%) 0 (0%) 0 (0%) 23s kube-system kube-scheduler-instance 100m (1%) 0 (0%) 0 (0%) 0 (0%) 26s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 26s 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 22s kube-proxy Normal NodeHasSufficientMemory 34s (x8 over 35s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 34s (x8 over 35s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 34s (x7 over 35s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 26s kubelet Starting kubelet. Warning InvalidDiskCapacity 26s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 26s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 26s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 26s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 23s node-controller Node instance event: Registered Node instance in Controller