Incident Library
Applied filters ComponentKubernetes API serverSymptomControl plane unresponsiveOrganisationLinodeClear 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

Cases1 case

1 to 1 of 1

  1. IL-0165 Some LKE users in Frankfurt could not reach their kube-apiservers with kubectl after backend services failed under memory constraints
    Linode2023
    Symptoms

    At 14:11 UTC on May 25, 2023, Linode learned that part of its LKE users in the Frankfurt data center could not reach their kube-apiservers through kubectl. The status page opened at 14:27 UTC with "We are investigating reports of connectivity issues with the LKE service within the Frankfurt Datacenter".

    Control plane unresponsive
    Root cause
    Capacity exhaustion
    Component
    Kubernetes API serverContainer memory limit
    Contributing factor
    –
    Detection

    Linode was made aware of the problem at 14:11 UTC; the status page refers to reports of connectivity issues.

    Remediation
    • increased memory limits
    Action items
    • Increase resilience, redundancy and monitoring for the LKE components affected by the incident
    View case
Check your cluster for this

This case involves Kubernetes API server and Container memory limit. 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

Capacity exhaustion1 case

Component
Kubernetes API serverContainer memory limit
Contributing factor
–
Organisation
Linode
  1. IL-0165 Some LKE users in Frankfurt could not reach their kube-apiservers with kubectl after backend services failed under memory constraints
    Linode2023