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, 07 Apr 2026 05:56:17 +0000 Taints: node.kubernetes.io/not-ready:NoExecute node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Tue, 07 Apr 2026 05:56:41 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Tue, 07 Apr 2026 05:56:21 +0000 Tue, 07 Apr 2026 05:56:15 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 07 Apr 2026 05:56:21 +0000 Tue, 07 Apr 2026 05:56:15 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 07 Apr 2026 05:56:21 +0000 Tue, 07 Apr 2026 05:56:15 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Tue, 07 Apr 2026 05:56:21 +0000 Tue, 07 Apr 2026 05:56:15 +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.115 Hostname: instance Capacity: cpu: 16 ephemeral-storage: 314156732Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65841448Ki pods: 110 Allocatable: cpu: 16 ephemeral-storage: 289526843732 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65739048Ki pods: 110 System Info: Machine ID: a0a42572629b4ed5bd1ab80d568d3638 System UUID: a0a42572-629b-4ed5-bd1a-b80d568d3638 Boot ID: 4f3e5942-70da-4061-8012-444524125f9e Kernel Version: 5.15.0-174-generic OS Image: Ubuntu 22.04.5 LTS Operating System: linux Architecture: amd64 Container Runtime Version: containerd://2.2.0 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%) 26s kube-system kube-apiserver-instance 250m (1%) 0 (0%) 0 (0%) 0 (0%) 27s kube-system kube-controller-manager-instance 200m (1%) 0 (0%) 0 (0%) 0 (0%) 29s kube-system kube-proxy-8b7xn 0 (0%) 0 (0%) 0 (0%) 0 (0%) 21s kube-system kube-scheduler-instance 100m (0%) 0 (0%) 0 (0%) 0 (0%) 27s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 29s 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 20s kube-proxy Normal Starting 33s kubelet Starting kubelet. Warning InvalidDiskCapacity 33s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 33s (x8 over 33s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 33s (x8 over 33s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 33s (x7 over 33s) 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 22s node-controller Node instance event: Registered Node instance in Controller