Name: controller-3 Roles: control-plane Labels: beta.kubernetes.io/arch=amd64 beta.kubernetes.io/os=linux kubernetes.io/arch=amd64 kubernetes.io/hostname=controller-3 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: Tue, 27 Oct 2026 18:25:24 +0000 Taints: Unschedulable: false Lease: HolderIdentity: controller-3 AcquireTime: RenewTime: Tue, 27 Oct 2026 18:47:25 +0000 Conditions: Type Status LastHeartbeatTime LastTransitionTime Reason Message ---- ------ ----------------- ------------------ ------ ------- NetworkUnavailable False Tue, 27 Oct 2026 18:26:26 +0000 Tue, 27 Oct 2026 18:26:26 +0000 CiliumIsUp Cilium is running on this node MemoryPressure False Tue, 27 Oct 2026 18:44:47 +0000 Tue, 27 Oct 2026 18:25:24 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available DiskPressure False Tue, 27 Oct 2026 18:44:47 +0000 Tue, 27 Oct 2026 18:25:24 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure PIDPressure False Tue, 27 Oct 2026 18:44:47 +0000 Tue, 27 Oct 2026 18:25:24 +0000 KubeletHasSufficientPID kubelet has sufficient PID available Ready True Tue, 27 Oct 2026 18:44:47 +0000 Tue, 27 Oct 2026 18:26:19 +0000 KubeletReady kubelet is posting ready status Addresses: InternalIP: 162.253.55.118 Hostname: controller-3 Capacity: cpu: 8 ephemeral-storage: 78124012Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16382184Ki pods: 110 Allocatable: cpu: 8 ephemeral-storage: 71999089340 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16279784Ki pods: 110 System Info: Machine ID: 8ebcad62855c4dc5b964dbb67663cb27 System UUID: 8ebcad62-855c-4dc5-b964-dbb67663cb27 Boot ID: 4ddfe16f-7837-4e70-8316-c8fe6b72009f Kernel Version: 6.12.113+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 --------- ---- ------------ ---------- --------------- ------------- --- kube-system cilium-operator-69d99df44c-hrjrt 0 (0%) 0 (0%) 0 (0%) 0 (0%) 21m kube-system cilium-snrrq 100m (1%) 0 (0%) 10Mi (0%) 0 (0%) 21m kube-system etcd-controller-3 100m (1%) 0 (0%) 100Mi (0%) 0 (0%) 6m45s kube-system kube-apiserver-controller-3 250m (3%) 0 (0%) 0 (0%) 0 (0%) 6m45s kube-system kube-controller-manager-controller-3 200m (2%) 0 (0%) 0 (0%) 0 (0%) 5m11s kube-system kube-proxy-6dbkx 0 (0%) 0 (0%) 0 (0%) 0 (0%) 6m45s kube-system kube-scheduler-controller-3 100m (1%) 0 (0%) 0 (0%) 0 (0%) 6m45s kube-system kube-vip-controller-3 0 (0%) 0 (0%) 0 (0%) 0 (0%) 6m45s Allocated resources: (Total limits may be over 100 percent, i.e., overcommitted.) Resource Requests Limits -------- -------- ------ cpu 750m (9%) 0 (0%) memory 110Mi (0%) 0 (0%) 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 21m kube-proxy Normal Starting 6m44s kube-proxy Normal RegisteredNode 22m node-controller Node controller-3 event: Registered Node controller-3 in Controller Normal RegisteredNode 18m node-controller Node controller-3 event: Registered Node controller-3 in Controller Normal RegisteredNode 12m node-controller Node controller-3 event: Registered Node controller-3 in Controller Normal RegisteredNode 9m12s node-controller Node controller-3 event: Registered Node controller-3 in Controller Normal Starting 6m46s kubelet Starting kubelet. Warning InvalidDiskCapacity 6m46s kubelet invalid capacity 0 on image filesystem Normal NodeAllocatableEnforced 6m46s kubelet Updated Node Allocatable limit across pods Normal NodeHasSufficientMemory 6m46s kubelet Node controller-3 status is now: NodeHasSufficientMemory Normal NodeHasNoDiskPressure 6m46s kubelet Node controller-3 status is now: NodeHasNoDiskPressure Normal NodeHasSufficientPID 6m46s kubelet Node controller-3 status is now: NodeHasSufficientPID