Emerging Service Issue - Linode Kubernetes Engine - Multiple Regions
Incident
Report for Linode
Resolved
We haven’t observed any additional issues with the LKE Control Plane pods, and will now consider this incident resolved. If you continue to experience problems, please open a Support ticket for assistance.
Monitoring
At this time we have been able to correct the LKE control plane pod issues across all regions. We will be monitoring this to ensure that it remains stable. If you are still experiencing issues, please open a Support ticket for assistance.
Identified
Our team has identified the issue affecting the LKE Control Plane Pods. We are working quickly to implement a fix, and we will provide an update as soon as the solution is in place.
Update
We are continuing to investigate this issue.
Investigating
Our team is investigating an emerging service issue affecting the Linode Kubernetes Engine in multiple regions. We will share additional updates as we have more information.
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, US-IAD (Washington) Linode Kubernetes Engine, US-ORD (Chicago) Linode Kubernetes Engine, CA-Central (Toronto) Linode Kubernetes Engine, EU-West (London) Linode Kubernetes Engine, EU-Central (Frankfurt) Linode Kubernetes Engine, FR-PAR (Paris) 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, SE-STO (Stockholm) Linode Kubernetes Engine, US-SEA (Seattle) Linode Kubernetes Engine, JP-OSA (Osaka) Linode Kubernetes Engine, IN-MAA (Chennai) Linode Kubernetes Engine, ID-CGK (Jakarta)).