Pods Stuck Pending After IP Pool Exhaustion: 5 Production Decisions for TKE Network Selection and Node Pool Governance
Overview 2 AM, phone buzzing with alerts. I open it up — 40+ pods in the TKE cluster suddenly enter Pending state, business APIs timing out across the board. A quick kubectl describe pod reveals the scheduling failure reason, crystal clear: Insufficient tke.cloud.tencent.com/eni-ip. This wasn’t some exotic technical puzzle. The root cause was straightforward: under VPC-CNI mode, the auxiliary IPs bound to the elastic network interfaces (ENIs) on the nodes were exhausted....