Back to all scenarios
Scenario #113
Networking
K8s v1.19, GKE

Pod Eviction Due to Network Resource Constraints

A pod was evicted due to network resource constraints, specifically limited bandwidth.

Find this helpful?
What Happened

The pod was evicted by the kubelet due to network resource limits being exceeded, leading to a failure in service availability.

Diagnosis Steps
  • 1Used kubectl describe pod to investigate the eviction event and noted network-related resource constraints in the pod eviction message.
  • 2Checked node network resource limits and found bandwidth throttling was causing evictions.
Root Cause

Insufficient network bandwidth allocation for the pod.

Fix/Workaround
• Increased network bandwidth limits on the affected node pool.
• Re-scheduled the pod on a node with higher bandwidth availability.
Lessons Learned

Network bandwidth limits can impact pod availability and performance.

How to Avoid
  • 1Monitor and adjust network resource allocations regularly.
  • 2Use appropriate pod resource requests and limits to prevent evictions.