Back to all scenarios
Scenario #78
Cluster Management
K8s v1.19, AWS EKS

ReplicaSet Scaling Issues Due to Resource Limits

The ReplicaSet failed to scale due to insufficient resources on the nodes.

Find this helpful?
What Happened

When attempting to scale a ReplicaSet, new pods failed to schedule due to a lack of available resources on the nodes.

Diagnosis Steps
  • 1Checked the resource usage on the nodes and found they were running at full capacity.
  • 2Analyzed ReplicaSet scaling events and observed failures to schedule new pods.
Root Cause

Insufficient node resources to accommodate new pods due to high resource consumption by existing workloads.

Fix/Workaround
• Added more nodes to the cluster to handle the increased workload.
• Adjusted resource requests and limits to ensure efficient resource allocation.
Lessons Learned

Regularly monitor cluster resource usage and scale proactively based on demand.

How to Avoid
  • 1Enable cluster autoscaling to handle scaling issues automatically.
  • 2Set proper resource requests and limits for pods to avoid resource exhaustion.
Previous ScenarioNext Scenario