Back to all scenarios
Scenario #449
Scaling & Load
Kubernetes v1.24, Google Cloud

Delayed Pod Creation Due to Node Affinity Misconfigurations

Pods were delayed in being created due to misconfigured node affinity rules during scaling events.

Find this helpful?
What Happened

Node affinity rules were too strict, leading to delays in pod scheduling when scaling up.

Diagnosis Steps
  • 1Reviewed node affinity rules and found they were unnecessarily restricting pod scheduling.
  • 2Observed that pods were stuck in the Pending state.
Root Cause

Overly restrictive node affinity rules caused delays in pod scheduling.

Fix/Workaround
• Loosened node affinity rules to allow more flexible scheduling.
• Used affinity rules more suited for scaling scenarios.
Lessons Learned

Node affinity must be carefully designed to allow for scaling flexibility.

How to Avoid
  • 1Test affinity rules in scaling scenarios to ensure they don't block pod scheduling.
  • 2Ensure that affinity rules are aligned with scaling requirements.