Incident Library
Applied filters Root causeSoftware defectComponentCloud load balancerSymptomNode NotReadyClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

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

Cases1 case

1 to 1 of 1

  1. IL-0030 Most nodes of a cluster went NotReady together for 15 minutes while the API server sat behind an AWS ELB
    Zalando2019
    Symptoms

    Fewer than 20% of the nodes in one Zalando cluster were available. Most nodes reported NotReady at the same moment, and only a handful stayed Ready.

    Node NotReady
    Root cause
    Software defect
    Component
    Kubernetes API serverCloud load balancer
    Contributing factor
    Unpatched known bug
    Remediation
    • none; the nodes recovered on their own after about 15 minutes
    View case
Check your cluster for this

This case involves Cloud load balancer and Kubernetes API server. 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
Cloud load balancerKubernetes API server
Contributing factor
Unpatched known bug
Organisation
Zalando
  1. IL-0030 Most nodes of a cluster went NotReady together for 15 minutes while the API server sat behind an AWS ELB
    Zalando2019