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: Sun, 22 Feb 2026 17:41:32 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Sun, 22 Feb 2026 17:43:28 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Sun, 22 Feb 2026 17:42:16 +0000 Sun, 22 Feb 2026 17:42:16 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Sun, 22 Feb 2026 17:42:36 +0000 Sun, 22 Feb 2026 17:41:30 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Sun, 22 Feb 2026 17:42:36 +0000 Sun, 22 Feb 2026 17:41:30 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Sun, 22 Feb 2026 17:42:36 +0000 Sun, 22 Feb 2026 17:41:30 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Sun, 22 Feb 2026 17:42:36 +0000 Sun, 22 Feb 2026 17:42:12 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 162.253.55.62 Hostname: instance Capacity: cpu: 8 ephemeral-storage: 78132668Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16372036Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 72007066710 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16269636Ki pods: 110 System Info: Machine ID: b0a7a6fe89584e3894aa9ea4d76b6bc2 System UUID: b0a7a6fe-8958-4e38-94aa-9ea4d76b6bc2 Boot ID: 413b4172-b979-4e7f-b1c2-6d61f2cc0702 Kernel Version: 5.15.0-170-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-4grzs 100m (1%) 0 (0%) 10Mi (0%) 0 (0%) 100s kube-system cilium-operator-7fcd8d6ffd-5zl2t 0 (0%) 0 (0%) 0 (0%) 0 (0%) 100s kube-system coredns-77cccfdc44-h8wv4 100m (1%) 0 (0%) 70Mi (0%) 170Mi (1%) 112s kube-system coredns-77cccfdc44-ztzhc 100m (1%) 0 (0%) 70Mi (0%) 170Mi (1%) 112s kube-system etcd-instance 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 2m2s kube-system kube-apiserver-instance 250m (3%) 0 (0%) 0 (0%) 0 (0%) 2m2s kube-system kube-controller-manager-instance 200m (2%) 0 (0%) 0 (0%) 0 (0%) 2m2s kube-system kube-proxy-24k4b 0 (0%) 0 (0%) 0 (0%) 0 (0%) 118s kube-system kube-scheduler-instance 100m (1%) 0 (0%) 0 (0%) 0 (0%) 2m4s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m5s local-path-storage local-path-provisioner-6f56467975-zr7tl 0 (0%) 0 (0%) 0 (0%) 0 (0%) 95s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 950m (11%) 0 (0%) memory 250Mi (1%) 340Mi (2%) 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 117s kube-proxy Normal Starting 2m2s kubelet Starting kubelet. Warning InvalidDiskCapacity 2m2s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 2m2s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 2m2s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 2m2s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 119s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 85s kubelet Node instance status is now: NodeReady