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= 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, 21 Apr 2026 19:17:54 +0000 Taints: Unschedulable: false Lease: HolderIdentity: instance AcquireTime: RenewTime: Tue, 21 Apr 2026 19:23:34 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- MemoryPressure False Tue, 21 Apr 2026 19:18:59 +0000 Tue, 21 Apr 2026 19:17:52 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 21 Apr 2026 19:18:59 +0000 Tue, 21 Apr 2026 19:17:52 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 21 Apr 2026 19:18:59 +0000 Tue, 21 Apr 2026 19:17:52 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Tue, 21 Apr 2026 19:18:59 +0000 Tue, 21 Apr 2026 19:18:42 +0000 KubeletReady kubelet is posting ready status. AppArmor enabled Addresses: InternalIP: 199.204.45.229 Hostname: instance Capacity: cpu: 8 ephemeral-storage: 78117196Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16372036Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 71992807715 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16269636Ki pods: 110 System Info: Machine ID: bc83a6e646be47168100935cfb2bc59b System UUID: bc83a6e6-46be-4716-8100-935cfb2bc59b Boot ID: 4ca31dfb-348b-4231-9912-06a53177f0d2 Kernel Version: 5.15.0-176-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: (10 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- envoy-gateway-system envoy-gateway-gateway-helm-certgen-pjjj7 0 (0%) 0 (0%) 0 (0%) 0 (0%) 5m6s kube-system cilium-operator-869df985b8-4mjsf 0 (0%) 0 (0%) 0 (0%) 0 (0%) 5m17s kube-system cilium-qz4jm 100m (1%) 0 (0%) 10Mi (0%) 0 (0%) 5m17s kube-system coredns-7c96b6546b-slkf6 100m (1%) 0 (0%) 70Mi (0%) 170Mi (1%) 5m36s kube-system etcd-instance 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 5m42s kube-system kube-apiserver-instance 250m (3%) 0 (0%) 0 (0%) 0 (0%) 5m44s kube-system kube-controller-manager-instance 200m (2%) 0 (0%) 0 (0%) 0 (0%) 5m42s kube-system kube-proxy-pbfpz 0 (0%) 0 (0%) 0 (0%) 0 (0%) 5m37s kube-system kube-scheduler-instance 100m (1%) 0 (0%) 0 (0%) 0 (0%) 5m42s kube-system kube-vip-instance 0 (0%) 0 (0%) 0 (0%) 0 (0%) 5m45s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 850m (10%) 0 (0%) memory 180Mi (1%) 170Mi (1%) 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 5m34s kube-proxy Normal Starting 5m48s kubelet Starting kubelet. Warning InvalidDiskCapacity 5m48s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 5m48s (x8 over 5m48s) kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 5m48s (x8 over 5m48s) kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 5m48s (x7 over 5m48s) kubelet Node instance status is now: NodeHasSufficientPID Normal Starting 5m42s kubelet Starting kubelet. Warning InvalidDiskCapacity 5m42s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 5m42s kubelet Node instance status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 5m42s kubelet Node instance status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 5m42s kubelet Node instance status is now: NodeHasSufficientPID Normal RegisteredNode 5m37s node-controller Node instance event: Registered Node instance in Controller Normal NodeReady 4m57s kubelet Node instance status is now: NodeReady