[{"id":"IL-0048","title":{"en":"DNS lookups timed out in a large EKS cluster when CoreDNS hit the 1024 packets-per-second link-local limit, driven by sudo hostname lookups","ko":"대형 EKS 클러스터에서 CoreDNS 가 VPC DNS 리졸버로 보내는 질의가 링크 로컬 트래픽의 초당 1024 패킷 한도에 걸려 DNS 조회가 간헐적으로 타임아웃됐다."},"org":"unknown","org_slug":"unknown","date":"2025-08-12","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0048","shared_components":["dns-resolver"]},{"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":["dns-resolver"]},{"id":"IL-0312","title":{"en":"Gadget's main Postgres did not start again after a restart to raise max_connections, and the platform went down","ko":"max_connections 를 올리려고 재시작한 주 PostgreSQL 데이터베이스가 다시 올라오지 않아 Gadget 의 모든 앱 요청이 멈췄다"},"org":"Gadget","org_slug":"gadget","date":"2024-12-13","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0312","shared_components":["linux-kernel"]},{"id":"IL-0433","title":{"en":"Shifting API traffic from EC2 to EKS on Fargate overloaded two CoreDNS pods and caused mass name-resolution errors","ko":"EC2 에서 EKS on Fargate 로 트래픽을 옮기던 중 CoreDNS 과부하로 이름 해석 오류가 쏟아져 롤백했다"},"org":"MonotaRO","org_slug":"monotaro","date":"2023-08-24","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0433","shared_components":["dns-resolver"]},{"id":"IL-0445","title":{"en":"Chatwork's service on EKS became unstable as conntrack tables on some nodes overflowed and connections were dropped","ko":"EKS 로 옮기던 레거시 시스템에서 conntrack 테이블이 넘쳐 연결이 끊겼고, 이어 CoreDNS 파드가 축출될 때와 node-local-dns 를 넣은 뒤에 DNS 오류가 났다"},"org":"Chatwork","org_slug":"chatwork","date":"2021-01-05","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0445","shared_components":["dns-resolver"]},{"id":"IL-0176","title":{"en":"Prometheus in a 235-node Kubernetes cluster crash-looped because over two million series exhausted host memory and the kernel OOM killer chose it first, as Burstable QoS gave it oom_score_adj 999","ko":"시계열 급증으로 호스트 메모리가 바닥나자 oom_score_adj 999 를 받은 Prometheus 컨테이너가 커널 OOM Killer 에게 먼저 죽어 CrashLoopBackOff 에 빠졌다."},"org":"LINE","org_slug":"line","date":"2020-07-10","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0176","shared_components":["linux-kernel"]},{"id":"IL-0578","title":{"en":"Static content behind an HAProxy load balancer in an OpenStack Octavia amphora was delayed by tens of seconds","ko":"HAProxy 로드 밸런서를 거치는 정적 콘텐츠 전송이 수십 초씩 늦어졌다"},"org":"GMO Pepabo","org_slug":"gmo-pepabo","date":"2020-06-26","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0578","shared_components":["linux-kernel"]},{"id":"IL-0033","title":{"en":"Uneven load across kube-dns pods and a DNS packets-per-second limit pushed service latency to 20 seconds","ko":"kube-dns 파드 사이의 트래픽 불균형과 DNS 초당 패킷 한도 때문에 외부 DNS 조회가 많은 여러 서비스의 지연 시간이 20초까지 늘었다"},"org":"Airbnb","org_slug":"airbnb","date":"2019-11-21","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0033","shared_components":["dns-resolver"]},{"id":"IL-0064","title":{"en":"CPU-heavy pods packed onto one Google Cloud node drove it to kernel panics, and the crash moved from node to node until the site was down","ko":"CPU 를 많이 쓰는 파드가 Google Cloud 노드 하나에 몰려 노드가 커널 패닉으로 죽었고, 다시 배치된 파드가 다음 노드를 또 죽이며 웹사이트와 API 가 멈췄다."},"org":"Moonlight","org_slug":"moonlight","date":"2019-01-18","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0064","shared_components":["linux-kernel"]},{"id":"IL-0472","title":{"en":"Node-to-pod traffic and DNS failed on Tinder's 605-node Flannel cluster when every node's ARP cache passed gc_thresh3","ko":"노드 605개 클러스터의 모든 노드에서 ARP 캐시가 넘쳐 노드와 파드 사이 통신과 DNS 조회가 끊겼다"},"org":"Tinder","org_slug":"tinder","date":"2019-01-08","severity":"unknown","root_cause":"capacity","url":"https://benchlet.com/incidentlib/app/cases/IL-0472","shared_components":["linux-kernel"]},{"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":["dns-resolver"]}]