[{"id":"IL-0102","title":{"en":"CoreDNS pods on a production EKS cluster ran out of memory under a burst of new pods, endpoints and nodes, taking down the Buildkite web UI, APIs and job dispatch","ko":"배포와 워커 오토스케일링 폭주가 겹치자 크기를 고정해 둔 CoreDNS 가 메모리 한도를 넘겨 재시작된 뒤 회복하지 못했고, Buildkite 사이트 전체가 약 30분 멈췄다."},"org":"Buildkite","org_slug":"buildkite","date":"2026-08-25","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0102","shared_components":["node-pool","memory-limit"]},{"id":"IL-0027","title":{"en":"All CoreDNS pods landed on one node, the node ran out of memory, and DNS for the whole service went down","ko":"CoreDNS 파드가 모두 한 노드에 몰린 채 그 노드의 메모리가 고갈되자 DNS 가 응답하지 못해 아이디어스 서비스 전체가 멈췄다"},"org":"Backpackr","org_slug":"backpackr","date":"2025-05-07","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0027","shared_components":["node-pool","memory-limit"]},{"id":"IL-0016","title":{"en":"Prometheus on the live cluster ran out of memory and was OOMKilled, and the monitoring node it ran on went NotReady","ko":"네임스페이스와 규칙이 늘어 live 클러스터의 Prometheus 가 메모리 부족으로 OOMKilled 되며 플랫폼 모니터링이 끊겼다"},"org":"UK Ministry of Justice","org_slug":"uk-ministry-of-justice","date":"2023-07-25","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0016","shared_components":["node-pool","memory-limit"]},{"id":"IL-0094","title":{"en":"Student pods filled the shared nodes of a JupyterHub cluster and starved the hub's core pods, freezing the hub","ko":"JupyterHub 클러스터에서 학생 파드가 노드의 CPU 와 메모리를 다 써서 자원 보장이 부족했던 코어 파드가 자원을 얻지 못했고, 허브 전체가 멈췄다."},"org":"2i2c","org_slug":"2i2c","date":"2020-10-28","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0094","shared_components":["node-pool","memory-limit"]},{"id":"IL-0155","title":{"en":"Some DOKS clusters in NYC1 saw intermittent DNS timeouts and NodeNotReady events because CoreDNS ran on shared-CPU Droplet worker nodes","ko":"NYC1 의 일부 DOKS 클러스터에서 공유 CPU 노드 위의 CoreDNS 때문에 DNS 가 간헐적으로 실패하고 NodeNotReady 가 났다"},"org":"DigitalOcean","org_slug":"digitalocean","date":"2026-07-09","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0155","shared_components":["node-pool"]},{"id":"IL-0100","title":{"en":"PostHog's feature flags pods were packed onto Kubernetes nodes that were too small for their CPU requests, and CPU saturation above 90% caused three outages in ten days through Redis overload, connection pool exhaustion and slow queries","ko":"노드가 파드의 CPU 요청에 비해 작아 CPU 가 포화되면서 PostHog 기능 플래그 서비스에 열흘 사이 장애가 세 번 났다."},"org":"PostHog","org_slug":"posthog","date":"2025-10-21","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0100","shared_components":["node-pool"]},{"id":"IL-0082","title":{"en":"Losing one CoreDNS pod during a planned EKS node reroll overloaded the remaining CoreDNS pods, causing DNS timeouts and errors across multiple services at RebelMouse","ko":"EKS 노드 교체 중 CoreDNS 파드 하나가 종료되자 남은 CoreDNS 파드가 늘어난 부하를 버티지 못해 DNS 조회가 느려지고 타임아웃이 났다."},"org":"RebelMouse","org_slug":"rebelmouse","date":"2025-05-19","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0082","shared_components":["node-pool"]},{"id":"IL-0044","title":{"en":"Prometheus OOMKilled in a loop while replaying its write-ahead log after a kube-prometheus-stack upgrade","ko":"kube-prometheus-stack 업그레이드 뒤 Prometheus 가 WAL 재생 중 메모리를 50Gi 넘게 써서 시작할 때마다 OOMKilled 로 죽었다"},"org":"Saifeddine Rajhi","org_slug":"saifeddine-rajhi","date":"2024-06-14","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0044","shared_components":["memory-limit"]},{"id":"IL-0110","title":{"en":"A Grafana Agent pod's high memory use and crash-looping Hangfire pods drove a Kubernetes node into system OOM and NotReady, twice in one day","ko":"Grafana Agent 파드가 메모리를 많이 쓰던 노드에 Hangfire 파드가 함께 올라가 시스템 OOM 으로 CrashLoopBackOff 를 반복했고, 노드가 응답을 멈추고 NotReady 가 됐다."},"org":"DFDS","org_slug":"dfds","date":"2024-03-13","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0110","shared_components":["memory-limit"]},{"id":"IL-0169","title":{"en":"The Scaleway Kubernetes API in FR-PAR ran out of memory under simultaneous deployments, and because it also handled node authentication, Kapsule and Kosmos nodes went NotReady","ko":"FR-PAR 의 Scaleway Kubernetes API 가 메모리 부족으로 쓰러져 노드 인증이 막히고 Kapsule 노드가 NotReady 가 됐다."},"org":"Scaleway","org_slug":"scaleway","date":"2024-01-24","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0169","shared_components":["memory-limit"]},{"id":"IL-0165","title":{"en":"Some LKE users in Frankfurt could not reach their kube-apiservers with kubectl after backend services failed under memory constraints","ko":"프랑크푸르트 LKE 의 백엔드 서비스가 메모리 부족으로 실패해 일부 사용자가 kubectl 로 kube-apiserver 에 접속하지 못했다"},"org":"Linode","org_slug":"linode","date":"2023-05-25","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0165","shared_components":["memory-limit"]},{"id":"IL-0070","title":{"en":"Critical pods on core nodes evicted when Prometheus began scraping about 200 nodes after a dask-gateway scale-up","ko":"dask-gateway로 워커를 대량으로 띄우자 노드가 1분 만에 100대 늘었고, Prometheus가 메모리를 거의 다 쓰던 코어 노드에서 hub 파드를 비롯한 중요한 파드들이 축출되거나 재시작됐다"},"org":"2i2c","org_slug":"2i2c","date":"2023-02-01","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0070","shared_components":["node-pool"]},{"id":"IL-0206","title":{"en":"Consul agents in GitLab.com's GKE pods were repeatedly OOM-killed, so the Rails pods lost database replica discovery and sent every query to the primary","ko":"GKE 파드 안의 Consul 에이전트가 메모리 급증으로 거듭 OOM kill 되어 Rails 파드가 데이터베이스 복제본을 찾지 못했고, 모든 쿼리가 primary 로 몰려 GitLab.com 이 느려졌다."},"org":"GitLab","org_slug":"gitlab","date":"2022-04-25","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0206","shared_components":["memory-limit"]},{"id":"IL-0013","title":{"en":"The conntrack table filled up on downsized GKE nodes and a high-traffic aggregation proxy saw climbing connection resets","ko":"노드 RAM 을 절반으로 줄이자 conntrack 테이블이 가득 차 집계 서비스에 연결 리셋과 오류가 늘었다"},"org":"loveholidays","org_slug":"loveholidays","date":"2020-02-15","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0013","shared_components":["node-pool"]},{"id":"IL-0015","title":{"en":"A GKE cluster's /16 pod address range ran out at 256 nodes, leaving new pods Pending and node scale-ups failing","ko":"GKE 가 노드마다 IP 256개를 미리 잡아 /16 파드 주소 범위가 바닥나고 노드 증설과 배포가 멈췄다"},"org":"loveholidays","org_slug":"loveholidays","date":"2020-02-03","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0015","shared_components":["node-pool"]},{"id":"IL-0026","title":{"en":"Kubernetes nodes hit SystemOOM because fluentd-sumologic log shipper pods had no memory limits","ko":"메모리 제한이 없는 fluentd-sumologic 파드가 메모리를 다 써서 운영 쿠버네티스 노드 두 대에 이틀 연속 SystemOOM 이 났다"},"org":"Blue Matador","org_slug":"blue-matador","date":"2019-06-15","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0026","shared_components":["memory-limit"]},{"id":"IL-0001","title":{"en":"Cluster-wide DNS outage after CoreDNS pods were OOM-killed again and again under a burst of DNS queries","ko":"CoreDNS 파드가 메모리 한도 100Mi 에 걸려 OOM 으로 계속 죽으면서 쿠버네티스 클러스터 전체의 DNS 가 멈췄다"},"org":"Zalando","org_slug":"zalando","date":"2019-01-07","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0001","shared_components":["memory-limit"]}]