Incident Library
  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. IL-0148 A kube-scheduler regression in Kubernetes v1.27.14, v1.28.10 and v1.29.5 made the scheduler panic on a pod whose node affinity named a nonexistent node, so no pods were scheduled on affected AKS clusters
    Microsoft Azure2024
    Symptoms

    On AKS clusters running Kubernetes v1.27.14, v1.28.10 or v1.29.5, kube-scheduler panicked whenever the cluster contained a pod with a bad node affinity, and from then on no pod in the cluster was scheduled.

    Pods Pending
    Trigger

    A pod in the cluster with a required node affinity whose matchFields term names a node that does not exist.

    Root cause
    Software defect
    Component
    Pod scheduling and placement
    Contributing factor
    –
    Detection

    The AKS team found the bug; the issue does not say how.

    Remediation
    • AKS engineers fixed the impacted clusters
    • Rolled out a fixed kube-scheduler to all regions, applied to clusters automatically
    View case
Check your cluster for this

This case involves Pod scheduling and placement. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

Open kubegap

By root cause1

Software defect1 case

Component
Pod scheduling and placement
Contributing factor
–
Organisation
Microsoft Azure
  1. IL-0148 A kube-scheduler regression in Kubernetes v1.27.14, v1.28.10 and v1.29.5 made the scheduler panic on a pod whose node affinity named a nonexistent node, so no pods were scheduled on affected AKS clusters
    Microsoft Azure2024