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= openstack-compute-node=enabled openstack-control-plane=enabled openvswitch=enabled 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: Mon, 02 Feb 2026 17:41:48 +0000 Taints: node.kubernetes.io/not-ready:NoSchedule Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Mon, 02 Feb 2026 17:42:41 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Mon, 02 Feb 2026 17:41:51 +0000 Mon, 02 Feb 2026 17:41:45 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Mon, 02 Feb 2026 17:41:51 +0000 Mon, 02 Feb 2026 17:41:45 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Mon, 02 Feb 2026 17:41:51 +0000 Mon, 02 Feb 2026 17:41:45 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready False Mon, 02 Feb 2026 17:41:51 +0000 Mon, 02 Feb 2026 17:41:45 +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.192 Hostname: instance Capacity: cpu: 2 ephemeral-storage: 38802332Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 8128328Ki pods: 110 Allocatable: cpu: 2 ephemeral-storage: 35760229112 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 8025928Ki pods: 110 System Info: Machine ID: 585ed3858d974cd194782cb4306e5a1f System UUID: 585ed385-8d97-4cd1-9478-2cb4306e5a1f Boot ID: 08049099-c9a0-4e6f-aa9a-7d30c29962bc Kernel Version: 5.15.0-164-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: (8 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- kube-system cilium-lkv7p 100m (5%) 0 (0%) 10Mi (0%) 0 (0%) 29s kube-system cilium-operator-7fcd8d6ffd-9lmbv 0 (0%) 0 (0%) 0 (0%) 0 (0%) 29s kube-system etcd-instance 100m (5%) 0 (0%) 100Mi (1%) 0 (0%) 55s kube-system kube-apiserver-instance 250m (12%) 0 (0%) 0 (0%) 0 (0%) 55s kube-system kube-controller-manager-instance 200m (10%) 0 (0%) 0 (0%) 0 (0%) 56s kube-system kube-proxy-7v8l7 0 (0%) 0 (0%) 0 (0%) 0 (0%) 50s kube-system kube-scheduler-instance 100m (5%) 0 (0%) 0 (0%) 0 (0%) 54s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 57s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 750m (37%) 0 (0%) memory 110Mi (1%) 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 49s kube-proxy Normal Starting 61s kubelet Starting kubelet. Warning InvalidDiskCapacity 61s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 61s (x8 over 61s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 61s (x8 over 61s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 61s (x7 over 61s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 54s kubelet Starting kubelet. Warning InvalidDiskCapacity 54s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 54s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 54s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 54s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 51s node-controller Node instance event: Registered Node instance in Controller