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: Thu, 30 Jul 2026 20:52:27 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Thu, 30 Jul 2026 20:53:53 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Thu, 30 Jul 2026 20:53:20 +0000 Thu, 30 Jul 2026 20:53:20 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Thu, 30 Jul 2026 20:53:32 +0000 Thu, 30 Jul 2026 20:52:26 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Thu, 30 Jul 2026 20:53:32 +0000 Thu, 30 Jul 2026 20:52:26 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Thu, 30 Jul 2026 20:53:32 +0000 Thu, 30 Jul 2026 20:52:26 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Thu, 30 Jul 2026 20:53:32 +0000 Thu, 30 Jul 2026 20:53:16 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 199.204.45.109 Hostname: instance Capacity: cpu: 16 ephemeral-storage: 314115704Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65841440Ki pods: 110 Allocatable: cpu: 16 ephemeral-storage: 289489032328 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65739040Ki pods: 110 System Info: Machine ID: a50612f326b44afabb8f613a88c05807 System UUID: a50612f3-26b4-4afa-bb8f-613a88c05807 Boot ID: b9230e9f-8c4c-40d6-8b63-dd56223855ef Kernel Version: 5.15.0-186-generic OS Image: Ubuntu 22.04.5 LTS Operating System: linux Architecture: amd64 Container Runtime Version: containerd://2.3.2 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 --------- ---- ------------ ---------- --------------- ------------- --- envoy-gateway-system envoy-gateway-78446f96c9-rn69b 100m (0%) 0 (0%) 256Mi (0%) 1Gi (1%) 33s kube-system cilium-8ccsv 100m (0%) 0 (0%) 10Mi (0%) 0 (0%) 60s kube-system cilium-operator-869df985b8-pdphb 0 (0%) 0 (0%) 0 (0%) 0 (0%) 60s kube-system coredns-67659f764b-2qn2s 100m (0%) 0 (0%) 70Mi (0%) 170Mi (0%) 72s kube-system coredns-67659f764b-sjhhk 100m (0%) 0 (0%) 70Mi (0%) 170Mi (0%) 72s kube-system etcd-instance 100m (0%) 0 (0%) 100Mi (0%) 0 (0%) 90s kube-system kube-apiserver-instance 250m (1%) 0 (0%) 0 (0%) 0 (0%) 90s kube-system kube-controller-manager-instance 200m (1%) 0 (0%) 0 (0%) 0 (0%) 90s kube-system kube-proxy-82lnl 0 (0%) 0 (0%) 0 (0%) 0 (0%) 85s kube-system kube-scheduler-instance 100m (0%) 0 (0%) 0 (0%) 0 (0%) 92s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 94s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 1050m (6%) 0 (0%) memory 506Mi (0%) 1364Mi (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 84s kube-proxy Normal Starting 90s kubelet Starting kubelet. Warning InvalidDiskCapacity 90s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 90s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 90s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 90s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 85s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 45s kubelet Node instance status is now: NodeReady