[{"id":"IL-0112","title":{"en":"The daily node rollover put DFDS's EKS nodes on an AMI later recalled for a kernel issue, causing \"PLEG is not healthy\" NodeNotReady flaps and pod network timeouts","ko":"나중에 회수된 EKS 노드 AMI 로 노드를 교체한 뒤 노드가 PLEG is not healthy 를 보고하며 NotReady 를 오갔고 파드 네트워크 타임아웃이 났다"},"org":"DFDS","org_slug":"dfds","date":"2022-10-31","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0112","shared_components":["kubelet","linux-kernel"]},{"id":"IL-0029","title":{"en":"Slow user-facing services from CPU throttling on containers that used far less CPU than their limit","ko":"CPU 한도를 건 컨테이너가 사용량이 한도에 한참 못 미치는데도 스로틀링되어 사용자 대면 서비스의 지연 시간이 늘었다."},"org":"Buffer","org_slug":"buffer","date":"2020-08-31","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0029","shared_components":["cpu-limit","linux-kernel"]},{"id":"IL-0138","title":{"en":"A failed Nvidia driver build left broken kernel packages on the only Kubernetes master node, which hit a kernel panic on reboot after a power outage and took the homelab cluster down for six days","ko":"nvidia-dkms-390 드라이버 빌드 실패로 망가진 커널 헤더가 몇 주 동안 방치됐다가, 정전 뒤 재부팅하자 하나뿐인 마스터 노드가 커널 패닉에 빠져 홈랩 쿠버네티스 클러스터가 6일 동안 멈췄다."},"org":"Barush Mendez","org_slug":"barush-mendez","date":"2025-03-03","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0138","shared_components":["linux-kernel"]},{"id":"IL-0139","title":{"en":"Pods on GKE clusters with Calico network policy got stuck Terminating or Pending after upgrading to 1.22 or later because of a race condition in the Calico component","ko":"Calico 네트워크 정책을 쓰는 GKE 클러스터를 1.22 이상으로 업그레이드하자 경쟁 조건 때문에 CNI 정리가 Unauthorized 로 실패해 파드가 Terminating 이나 Pending 에 멈췄다."},"org":"Google Cloud","org_slug":"google-cloud","date":"2022-09-15","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0139","shared_components":["kubelet"]},{"id":"IL-0175","title":{"en":"Lowering a JVM pod's CPU request from 2 to 1 pushed memory past the 90% alert because the JVM treats a cgroup v1 cpu.shares value of exactly 1024 as unset and sized Reactor Netty threads from the node's 36 CPUs","ko":"JVM 파드의 CPU requests 를 1코어로 줄이자 JVM 이 노드의 CPU 36개를 인식해 Reactor Netty 스레드가 늘고 메모리 사용량이 경보 기준을 넘었다"},"org":"Hyperconnect","org_slug":"hyperconnect","date":"2022-07-19","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0175","shared_components":["cpu-limit"]},{"id":"IL-0143","title":{"en":"GKE nodes upgraded to certain 1.13 and 1.14 versions had an elevated number of kernel panics, fixed by releases that downgraded the Container-Optimized OS image","ko":"GKE 1.13 과 1.14 의 특정 버전으로 업그레이드한 노드에서 커널 패닉이 늘었다."},"org":"Google Cloud","org_slug":"google-cloud","date":"2019-11-04","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0143","shared_components":["linux-kernel"]},{"id":"IL-0074","title":{"en":"All AirMap platform services down as worker nodes went NotReady and pods crash-looped on network and DNS failures","ko":"워커 노드가 잇달아 Not Ready 에 빠지고 네트워크와 DNS 실패로 사이드카가 죽으면서, AirMap 플랫폼의 모든 서비스가 다섯 시간 동안 응답하지 않았다."},"org":"AirMap","org_slug":"airmap","date":"2018-07-19","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0074","shared_components":["kubelet"]},{"id":"IL-0038","title":{"en":"kubelet rollout hit a Kubernetes bug and left every node in a cluster NotReady, triggering mass pod eviction","ko":"kubelet 설정 변경을 롤링 업데이트하다 쿠버네티스 버그로 kubelet 이 올라오지 못해 한 클러스터의 노드가 NotReady 가 되고 파드 절반쯤이 축출됐다"},"org":"Oath","org_slug":"oath","date":"2018-05-04","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0038","shared_components":["kubelet"]},{"id":"IL-0003","title":{"en":"linkerd lost Kubernetes service discovery after an etcd reconfiguration, and restarting every linkerd instance turned failed payments into a full platform outage","ko":"etcd 클러스터 재구성 뒤 쿠버네티스 버그로 linkerd 가 서비스 위치 갱신을 받지 못했고, linkerd 를 모두 재시작하자 엔드포인트가 없는 서비스를 파싱하지 못하는 오류가 드러나 플랫폼 전체가 멈췄다"},"org":"Monzo","org_slug":"monzo","date":"2017-10-27","severity":"unknown","root_cause":"software-bug","url":"https://benchlet.com/incidentlib/app/cases/IL-0003","shared_components":["kubelet"]}]