Incident Library
Applied filters Root causeCertificate or credential expiryOrganisationLinodeClear 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

Cases2 cases

1 to 2 of 2

  1. IL-0158 An expired credential caused authentication failures that stopped LKE and LKE-E from deploying clusters and nodes in all regions, which also blocked node recycling and cluster autoscaling
    Linode2026
    Symptoms

    From 11:45 UTC on 16 April 2026, customers of Linode Kubernetes Engine (LKE) and Linode Kubernetes Engine Enterprise (LKE-E) could not deploy new clusters or add new nodes to existing clusters. Because no new node could be deployed, node recycling and cluster autoscaling did not work either. The problem hit every region where LKE runs.

    Deploys failingScale-up failureCredentials unavailable
    Trigger

    A credential expired, which caused authentication failures when LKE and LKE-E deployed clusters and nodes. One status update describes it as an expired certificate.

    Root cause
    Certificate or credential expiry
    Component
    Node pool
    Contributing factor
    –
    Detection

    The first status page update, saying the team was investigating an emerging issue affecting LKE and LKE-E in all regions, was posted at 13:20 UTC.

    Remediation
    • created new credentials and deployed them, rotating the expired credential (certificate)
    Action items
    • Investigate what led to the credential expiry and take preventive actions
    Lessons

    One expired credential stopped every operation that needs a new node, in all regions at once: new clusters, added nodes, node recycling and autoscaling.

    View case
  2. IL-0156 Revoking old certificates after a rotation left a certificate key mismatch between API endpoints and the cluster controller, and LKE cluster management and autoscaling in Atlanta returned 5xx errors
    Linode2025
    Symptoms

    From about 02:29 UTC on 24 September 2025, customers of Linode Kubernetes Engine (LKE) in US-Southeast (Atlanta) could not manage their clusters, and autoscaling was impacted. Internal logs showed 5xx errors whenever customers tried to manage LKE clusters associated with the affected cluster controller.

    High error rateAutoscaler misbehaviour
    Trigger

    Old certificates on the LKE cluster controllers were revoked at 02:29 UTC on 24 September 2025, after the expiring certificates had been rotated on 23 September.

    Root cause
    Certificate or credential expiry
    Component
    Managed Kubernetes control plane and provider APICluster autoscaler
    Contributing factor
    Change with a delayed effect
    Remediation
    • deployed a fix for the certificate key mismatch
    • restarted the API endpoints
    Action items
    • Continue investigating the root cause and take preventive actions
    View case
Check your cluster for this

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

Certificate or credential expiry2 cases

Component
Cluster autoscaler1Managed Kubernetes control plane and provider API1Node pool1
Contributing factor
Change with a delayed effect1
Organisation
Linode2
  1. IL-0158 An expired credential caused authentication failures that stopped LKE and LKE-E from deploying clusters and nodes in all regions, which also blocked node recycling and cluster autoscaling
    Linode2026
  2. IL-0156 Revoking old certificates after a rotation left a certificate key mismatch between API endpoints and the cluster controller, and LKE cluster management and autoscaling in Atlanta returned 5xx errors
    Linode2025