Name: controller-1 Roles: control-plane Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname=controller-1 kubernetes.io/os=linux node-role.kubernetes.io/control-plane= node.kubernetes.io/exclude-from-external-load-balancers= Annotations: node.alpha.kubernetes.io/ttl: 0 volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp: Thu, 10 Sep 2026 21:29:30 +0000 Taints: Unschedulable: false Lease: HolderIdentity: controller-1 AcquireTime: RenewTime: Thu, 10 Sep 2026 21:34:28 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Thu, 10 Sep 2026 21:32:39 +0000 Thu, 10 Sep 2026 21:32:39 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Thu, 10 Sep 2026 21:33:08 +0000 Thu, 10 Sep 2026 21:29:30 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Thu, 10 Sep 2026 21:33:08 +0000 Thu, 10 Sep 2026 21:29:30 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Thu, 10 Sep 2026 21:33:08 +0000 Thu, 10 Sep 2026 21:29:30 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Thu, 10 Sep 2026 21:33:08 +0000 Thu, 10 Sep 2026 21:32:37 +0000 KubeletReady kubelet is posting ready status Addresses: InternalIP: 162.253.55.128 Hostname: controller-1 Capacity: cpu: 8 ephemeral-storage: 78126572Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16382180Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 72001448636 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16279780Ki pods: 110 System Info: Machine ID: f5b7a3c15d3e410b83f8ffa8a7b27a2c System UUID: f5b7a3c1-5d3e-410b-83f8-ffa8a7b27a2c Boot ID: 3d9aad92-2f08-470f-ae37-55e3484a666f Kernel Version: 6.12.107+deb13-amd64 OS Image: Debian GNU/Linux 13 (trixie) Operating System: linux Architecture: amd64 Container Runtime Version: containerd://2.3.2 Kubelet Version: v1.34.0 Kube-Proxy Version: Non-terminated Pods: (8 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age --------- ---- ------------ ---------- --------------- ------------- --- envoy-gateway-system envoy-gateway-86c8f9f5d8-lgb7b 100m (1%) 0 (0%) 256Mi (1%) 1Gi (6%) 111s kube-system cilium-dnbcz 100m (1%) 0 (0%) 10Mi (0%) 0 (0%) 2m27s kube-system etcd-controller-1 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 5m5s kube-system kube-apiserver-controller-1 250m (3%) 0 (0%) 0 (0%) 0 (0%) 5m5s kube-system kube-controller-manager-controller-1 200m (2%) 0 (0%) 0 (0%) 0 (0%) 5m5s kube-system kube-proxy-8z96m 0 (0%) 0 (0%) 0 (0%) 0 (0%) 4m58s kube-system kube-scheduler-controller-1 100m (1%) 0 (0%) 0 (0%) 0 (0%) 5m5s kube-system kube-vip-controller-1 0 (0%) 0 (0%) 0 (0%) 0 (0%) 5m5s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 850m (10%) 0 (0%) memory 366Mi (2%) 1Gi (6%) 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 4m56s kube-proxy Normal NodeHasSufficientMemory 5m11s (x8 over 5m11s) kubelet Node controller-1 status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 5m11s (x8 over 5m11s) kubelet Node controller-1 status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 5m11s (x8 over 5m11s) kubelet Node controller-1 status is now: NodeHasSufficientPID Normal Starting 5m2s kubelet Starting kubelet. Warning InvalidDiskCapacity 5m2s kubelet invalid capacity 0 on image filesystem Normal NodeHasSufficientMemory 5m2s kubelet Node controller-1 status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 5m2s kubelet Node controller-1 status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 5m2s kubelet Node controller-1 status is now: NodeHasSufficientPID Normal RegisteredNode 4m59s node-controller Node controller-1 event: Registered Node controller-1 in Controller Normal NodeReady 118s kubelet Node controller-1 status is now: NodeReady