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: Tue, 24 Feb 2026 08:09:53 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Tue, 24 Feb 2026 08:11:49 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Tue, 24 Feb 2026 08:10:43 +0000 Tue, 24 Feb 2026 08:10:43 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Tue, 24 Feb 2026 08:11:58 +0000 Tue, 24 Feb 2026 08:09:51 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 24 Feb 2026 08:11:58 +0000 Tue, 24 Feb 2026 08:09:51 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 24 Feb 2026 08:11:58 +0000 Tue, 24 Feb 2026 08:09:51 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Tue, 24 Feb 2026 08:11:58 +0000 Tue, 24 Feb 2026 08:10:35 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 199.19.213.86 Hostname: instance Capacity: cpu: 8 ephemeral-storage: 78132668Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16372040Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 72007066710 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16269640Ki pods: 110 System Info: Machine ID: 6eec2e2103dc4051bf2deaecdd0b0eef System UUID: 6eec2e21-03dc-4051-bf2d-eaecdd0b0eef Boot ID: 48e2f913-da86-405b-b2c2-416d44a8c3af 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-8phz2 100m (1%) 0 (0%) 10Mi (0%) 0 (0%) 101s kube-system cilium-operator-7fcd8d6ffd-g7xc6 0 (0%) 0 (0%) 0 (0%) 0 (0%) 101s kube-system coredns-77cccfdc44-78whg 100m (1%) 0 (0%) 70Mi (0%) 170Mi (1%) 112s kube-system coredns-77cccfdc44-ckbjz 100m (1%) 0 (0%) 70Mi (0%) 170Mi (1%) 112s kube-system etcd-instance 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 2m3s kube-system kube-apiserver-instance 250m (3%) 0 (0%) 0 (0%) 0 (0%) 2m3s kube-system kube-controller-manager-instance 200m (2%) 0 (0%) 0 (0%) 0 (0%) 2m3s kube-system kube-proxy-x5dfg 0 (0%) 0 (0%) 0 (0%) 0 (0%) 118s kube-system kube-scheduler-instance 100m (1%) 0 (0%) 0 (0%) 0 (0%) 2m3s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 2m5s local-path-storage local-path-provisioner-6f56467975-j6cqx 0 (0%) 0 (0%) 0 (0%) 0 (0%) 96s 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 2m3s kubelet Starting kubelet. Warning InvalidDiskCapacity 2m3s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 2m3s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 2m3s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 2m3s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 119s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 84s kubelet Node instance status is now: NodeReady