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: Sat, 07 Feb 2026 03:53:25 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Sat, 07 Feb 2026 03:55:20 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Sat, 07 Feb 2026 03:54:10 +0000 Sat, 07 Feb 2026 03:54:10 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Sat, 07 Feb 2026 03:54:29 +0000 Sat, 07 Feb 2026 03:53:24 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Sat, 07 Feb 2026 03:54:29 +0000 Sat, 07 Feb 2026 03:53:24 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Sat, 07 Feb 2026 03:54:29 +0000 Sat, 07 Feb 2026 03:53:24 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Sat, 07 Feb 2026 03:54:29 +0000 Sat, 07 Feb 2026 03:54:05 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 162.253.55.200 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: fd47d8fb1ee54faea330296c746c4be8 System UUID: fd47d8fb-1ee5-4fae-a330-296c746c4be8 Boot ID: b431b0e8-fe8c-4e8e-a562-01a8808f9e63 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-ftpvl 100m (5%) 0 (0%) 10Mi (0%) 0 (0%) 98s kube-system cilium-operator-7fcd8d6ffd-5k2x6 0 (0%) 0 (0%) 0 (0%) 0 (0%) 98s kube-system coredns-77cccfdc44-f4pst 100m (5%) 0 (0%) 70Mi (0%) 170Mi (2%) 109s kube-system coredns-77cccfdc44-fcpc9 100m (5%) 0 (0%) 70Mi (0%) 170Mi (2%) 109s kube-system etcd-instance 100m (5%) 0 (0%) 100Mi (1%) 0 (0%) 119s kube-system kube-apiserver-instance 250m (12%) 0 (0%) 0 (0%) 0 (0%) 119s kube-system kube-controller-manager-instance 200m (10%) 0 (0%) 0 (0%) 0 (0%) 119s kube-system kube-proxy-gt65q 0 (0%) 0 (0%) 0 (0%) 0 (0%) 114s kube-system kube-scheduler-instance 100m (5%) 0 (0%) 0 (0%) 0 (0%) 119s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 119s local-path-storage local-path-provisioner-6f56467975-6gh2g 0 (0%) 0 (0%) 0 (0%) 0 (0%) 93s 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 112s kube-proxy Normal Starting 119s kubelet Starting kubelet. Warning InvalidDiskCapacity 119s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 119s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 119s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 119s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 115s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 82s kubelet Node instance status is now: NodeReady