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, 09 Feb 2026 18:49:22 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Mon, 09 Feb 2026 18:51:29 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Mon, 09 Feb 2026 18:50:07 +0000 Mon, 09 Feb 2026 18:50:07 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Mon, 09 Feb 2026 18:51:30 +0000 Mon, 09 Feb 2026 18:49:21 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Mon, 09 Feb 2026 18:51:30 +0000 Mon, 09 Feb 2026 18:49:21 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Mon, 09 Feb 2026 18:51:30 +0000 Mon, 09 Feb 2026 18:49:21 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Mon, 09 Feb 2026 18:51:30 +0000 Mon, 09 Feb 2026 18:50:04 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 199.204.45.225 Hostname: instance Capacity: cpu: 2 ephemeral-storage: 38801004Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 8128336Ki pods: 110 Allocatable: cpu: 2 ephemeral-storage: 35759005228 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 8025936Ki pods: 110 System Info: Machine ID: c47fc7dc198b45748d2bd675f705f65a System UUID: c47fc7dc-198b-4574-8d2b-d675f705f65a Boot ID: be0e0574-84f6-40df-93e2-f9fe200c7982 Kernel Version: 5.15.0-168-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: (11 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- kube-system cilium-ln8xr 100m (5%) 0 (0%) 10Mi (0%) 0 (0%) 103s kube-system cilium-operator-7fcd8d6ffd-vz7cr 0 (0%) 0 (0%) 0 (0%) 0 (0%) 103s kube-system coredns-77cccfdc44-9zzbs 100m (5%) 0 (0%) 70Mi (0%) 170Mi (2%) 114s kube-system coredns-77cccfdc44-v67tt 100m (5%) 0 (0%) 70Mi (0%) 170Mi (2%) 114s kube-system etcd-instance 100m (5%) 0 (0%) 100Mi (1%) 0 (0%) 2m4s kube-system kube-apiserver-instance 250m (12%) 0 (0%) 0 (0%) 0 (0%) 2m4s kube-system kube-controller-manager-instance 200m (10%) 0 (0%) 0 (0%) 0 (0%) 2m4s kube-system kube-proxy-qbg5z 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m1s kube-system kube-scheduler-instance 100m (5%) 0 (0%) 0 (0%) 0 (0%) 2m4s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m7s local-path-storage local-path-provisioner-6f56467975-2qgxq 0 (0%) 0 (0%) 0 (0%) 0 (0%) 98s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 950m (47%) 0 (0%) memory 250Mi (3%) 340Mi (4%) 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 119s kube-proxy Normal Starting 2m11s kubelet Starting kubelet. Warning InvalidDiskCapacity 2m11s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 2m11s (x8 over 2m11s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 2m11s (x8 over 2m11s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 2m11s (x7 over 2m11s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 2m4s kubelet Starting kubelet. Warning InvalidDiskCapacity 2m4s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 2m4s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 2m4s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 2m4s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 2m1s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 86s kubelet Node instance status is now: NodeReady