IL-0167 Linode · 2026-03-12kubernetes
Starting around 19:15 UTC on 12 March 2026, creating LKE-E clusters in the Osaka data center (JP-OSA) stalled indefinitely, and administrative tasks such as LKE-E version upgrades and control plane ACL changes did not work. Akamai's investigation found that the problem began after a phased rollout of the LKE software release in that data center.
Akamai deployed a software fix, which mitigated the impact around 01:55 UTC on 13 March 2026, and clusters whose creation had stalled during the window resumed. The report, posted at 02:59 UTC the same day, says the root cause was still being investigated.
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.
Administrative tasks on LKE-E clusters there, such as version upgrades and control plane ACL changes, could not be performed either. The status page first posted an investigation into the deployment of new LKE Enterprise clusters in Osaka at 00:45 UTC on 13 March.
Root cause ? Faulty deployment
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.
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.
–