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, 26 May 2026 05:53:37 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Tue, 26 May 2026 05:54:42 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Tue, 26 May 2026 05:54:24 +0000 Tue, 26 May 2026 05:54:24 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Tue, 26 May 2026 05:54:42 +0000 Tue, 26 May 2026 05:53:36 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 26 May 2026 05:54:42 +0000 Tue, 26 May 2026 05:53:36 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 26 May 2026 05:54:42 +0000 Tue, 26 May 2026 05:53:36 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Tue, 26 May 2026 05:54:42 +0000 Tue, 26 May 2026 05:54:19 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 199.204.45.242 Hostname: instance Capacity: cpu: 16 ephemeral-storage: 314136184Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65841444Ki pods: 110 Allocatable: cpu: 16 ephemeral-storage: 289507906696 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 65739044Ki pods: 110 System Info: Machine ID: a76aa43c164345f4b25de1e4bf4d7819 System UUID: a76aa43c-1643-45f4-b25d-e1e4bf4d7819 Boot ID: 619b7dfd-ff68-4ba1-8a6b-45cf9959bdf3 Kernel Version: 5.15.0-179-generic OS Image: Ubuntu 22.04.5 LTS Operating System: linux Architecture: amd64 Container Runtime Version: containerd://2.2.3 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-rn9rg 100m (0%) 0 (0%) 256Mi (0%) 1Gi (1%) 14s kube-system cilium-kgxfk 100m (0%) 0 (0%) 10Mi (0%) 0 (0%) 45s kube-system cilium-operator-869df985b8-wm86b 0 (0%) 0 (0%) 0 (0%) 0 (0%) 45s kube-system coredns-67659f764b-6d6hm 100m (0%) 0 (0%) 70Mi (0%) 170Mi (0%) 60s kube-system coredns-67659f764b-pr66s 100m (0%) 0 (0%) 70Mi (0%) 170Mi (0%) 60s kube-system etcd-instance 100m (0%) 0 (0%) 100Mi (0%) 0 (0%) 69s kube-system kube-apiserver-instance 250m (1%) 0 (0%) 0 (0%) 0 (0%) 67s kube-system kube-controller-manager-instance 200m (1%) 0 (0%) 0 (0%) 0 (0%) 67s kube-system kube-proxy-mpf56 0 (0%) 0 (0%) 0 (0%) 0 (0%) 63s kube-system kube-scheduler-instance 100m (0%) 0 (0%) 0 (0%) 0 (0%) 68s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 69s 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 62s kube-proxy Normal Starting 67s kubelet Starting kubelet. Warning InvalidDiskCapacity 67s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 67s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 67s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 67s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 64s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 28s kubelet Node instance status is now: NodeReady