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

Cases2 cases

1 to 2 of 2

  1. IL-0167 A phased rollout of an LKE software release in Osaka stalled LKE-E cluster creation, version upgrades and control plane ACL changes
    Linode2026
    Symptoms

    From about 19:15 UTC on 12 March 2026, customers in the Osaka data center (JP-OSA) could not create Linode Kubernetes Engine for Enterprise (LKE-E) clusters. Cluster creation stalled indefinitely.

    Cluster or node provisioning stallUpgrade stall
    Trigger

    A phased rollout of the LKE software release reached the Osaka data center.

    Root cause
    Faulty deployment
    Component
    Managed Kubernetes control plane and provider API
    Contributing factor
    –
    Detection

    The problem began at about 19:15 UTC, and the first status post, about five and a half hours later at 00:45 UTC on 13 March, said the team was investigating an emerging issue with deploying new LKE Enterprise clusters in Osaka.

    Remediation
    • deployed a software fix to mitigate the impact
    Action items
    • Investigate the root cause further and take preventive actions
    Lessons

    The problem followed a phased rollout of an LKE software release in the Osaka data center. There, cluster creation and administrative tasks stalled for more than six hours, and the first status post came about five and a half hours after the start.

    View case
  2. IL-0164 An incremental Linode Kubernetes Engine production update that was missing changes from the previous release made cluster upgrades and node additions fail silently
    Linode2022
    Symptoms

    From about 18:30 UTC on June 15, 2022, customers of the Linode Kubernetes Engine (LKE) who tried to upgrade a cluster or add nodes saw those operations fail silently, without an error. The status page opened an investigation of an LKE issue at 19:54 UTC, and the affected list covered LKE in eleven regions.

    Upgrade stall
    Trigger

    An incremental update pushed to the LKE production environment at about 18:30 UTC.

    Root cause
    Faulty deployment
    Component
    Node pool
    Contributing factor
    –
    Detection

    The status page began investigating at 19:54 UTC, 1 hour 24 minutes after the update.

    Remediation
    • Released a follow-up LKE update at about 21:00 UTC that contained the missing changes
    Action items
    • Add steps and automation to the update process
    View case
Check your cluster for this

These 2 cases involve Managed Kubernetes control plane and provider API and Node pool. 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

Faulty deployment2 cases

Component
Managed Kubernetes control plane and provider API1Node pool1
Contributing factor
–
Organisation
Linode2
  1. IL-0167 A phased rollout of an LKE software release in Osaka stalled LKE-E cluster creation, version upgrades and control plane ACL changes
    Linode2026
  2. IL-0164 An incremental Linode Kubernetes Engine production update that was missing changes from the previous release made cluster upgrades and node additions fail silently
    Linode2022