Linode Status

Current Status
Service Issue - Linode Kubernetes Engine
Incident Report for Linode
Postmortem

On May 31st, at approximately 1600 UTC, a change was introduced to the API that caused LKE clusters to improperly scale. A gap in our automated testing did not capture this failure case, and this change was pushed to production. This caused some customer clusters to resize in unexpected ways and introduced additional billable resources to affected customer accounts. 

Once identified, a hotfix was implemented to correct this behavior at 09:40 UTC June 1st. Additional worker nodes were left in place in order to prevent impacting customer workload. Affected customers were alerted via ticket for credit adjustments and instructions for further mitigation. 

As a result of this incident, we will be auditing our tests and have created additional pre-deployment checklist items to ensure that this does not happen again.

Posted Jun 22, 2023 - 15:21 UTC

Resolved
At this time, the bug that caused this problem should be entirely fixed and affected Customers have been ticketed.

If you are still having any issues relating to this incident or anything else, please don't hesitate to reply to your Support ticket or create a new Support ticket.
Posted Jun 01, 2023 - 21:23 UTC
Update
We are continuing to monitor the fix implemented to address the bug. We are also working to address any impacted customers who may have had their LKE Node Pools incorrectly scaled and are accruing charges for the erroneously deployed services.
Posted Jun 01, 2023 - 11:57 UTC
Monitoring
A fix has been deployed to address the scaling issue that impacted LKE clusters. We will continue to monitor this situation and update this status page as necessary.
Posted Jun 01, 2023 - 10:20 UTC
Identified
Our team has identified what's causing the incorrect number of nodes to be generated when resizing LKE clusters and are working on implementing a fix. We will update this page once we have additional information to provide.
Posted Jun 01, 2023 - 08:56 UTC
Update
We are continuing to investigate this issue.
Posted Jun 01, 2023 - 07:06 UTC
Investigating
We have been made aware of an issue when resizing LKE clusters, resulting in an incorrect number of nodes being generated. It should be noted that the functioning of the cluster itself is not affected by this. As we work to resolve this, we advise customers to avoid resizing their clusters if possible.

Any overages caused by incorrectly provisioned nodes will be credited once the source of the issue has been resolved. If you encounter a situation where you have been overcharged for a LKE cluster due to this issue and have an immediate need of billing assistance, please open a Support ticket for assistance.
Posted Jun 01, 2023 - 05:07 UTC
This incident affected: Linode Kubernetes Engine (US-East (Newark) Linode Kubernetes Engine, US-Central (Dallas) Linode Kubernetes Engine, US-West (Fremont) Linode Kubernetes Engine, US-Southeast (Atlanta) Linode Kubernetes Engine, CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt) Linode Kubernetes Engine, AP-South (Singapore) Linode Kubernetes Engine, AP-Northeast-2 (Tokyo 2) Linode Kubernetes Engine, AP-West (Mumbai) Linode Kubernetes Engine, AP-Southeast (Sydney) Linode Kubernetes Engine).