[{"id":"IL-0101","title":{"en":"After Google forced a GKE control plane upgrade to 1.33.2 at a deprecation deadline, no new node could initialise, so autoscaling and spot node replacement stopped for 15 hours","ko":"자동 업그레이드를 꺼 둔 GKE 클러스터의 컨트롤 플레인이 지원 종료 기한에 1.33.2 로 강제 업그레이드된 뒤 새 노드가 모두 초기화에 실패해, 오토스케일링과 스팟 노드 복구가 15시간 멈췄다."},"org":"Wealthy","org_slug":"wealthy","date":"2025-09-14","severity":"sev1","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0101","shared_components":["node-pool"]},{"id":"IL-0120","title":{"en":"A daily scheduled OS update restarted systemd-networkd on cloud-hosted GPU nodes, which conflicted with OpenAI's networking agent and removed all routes, cutting capacity for ChatGPT and the API","ko":"클라우드 GPU 서버의 정기 OS 업데이트가 systemd-networkd 를 재시작해 자체 네트워크 에이전트와 충돌했고, 많은 GPU 노드의 라우트가 모두 지워져 ChatGPT 와 API 의 오류율이 크게 올랐다."},"org":"OpenAI","org_slug":"openai","date":"2025-06-09","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0120","shared_components":["node-image"]},{"id":"IL-0079","title":{"en":"A GKE node auto-upgrade to an ubuntu_containerd image with a kernel regression left kube-proxy unable to apply its ip6tables rules, so load balancer health checks failed and several clusters lost all ingress traffic","ko":"GKE 노드가 새 ubuntu_containerd 이미지로 자동 업그레이드된 뒤 커널에서 kube-proxy 가 쓰는 iptables 확장이 빠져, 여러 GKE 클러스터의 인그레스 트래픽이 완전히 끊겼다."},"org":"Altinity","org_slug":"altinity","date":"2025-05-17","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0079","shared_components":["node-image"]},{"id":"IL-0404","title":{"en":"All BSEE SaaS customer pods on EKS crash-looped after Karpenter moved nodes to Bottlerocket v1.26.0, which broke Java","ko":"Karpenter 가 운영 EKS 노드를 Bottlerocket v1.26.0 으로 바꾼 뒤 BSEE SaaS 고객 인스턴스의 파드가 모두 crash loop back off 에 빠졌다"},"org":"PortSwigger","org_slug":"portswigger","date":"2024-10-24","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0404","shared_components":["node-image"]},{"id":"IL-0198","title":{"en":"An automatic Ubuntu security update restarted systemd-networkd, which flushed the IP rules Cilium relied on and cut more than 60 percent of Datadog's Kubernetes nodes off the network across regions and cloud providers","ko":"systemd 보안 패치가 Ubuntu 22.04 노드의 systemd-networkd 를 재시작해 Cilium 이 넣은 IP 규칙을 지웠고, 여러 리전과 세 클라우드의 Kubernetes 노드가 한꺼번에 네트워크를 잃었다."},"org":"Datadog","org_slug":"datadog","date":"2023-03-08","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0198","shared_components":["node-image"]},{"id":"IL-0501","title":{"en":"Every node of the UToronto Kubernetes cluster on Azure went NotReady and the JupyterHub became unreachable","ko":"Azure 가 배포한 Ubuntu 18.04 업데이트로 UToronto AKS 클러스터의 모든 노드에서 네트워크가 끊겨 허브에 접속할 수 없었다"},"org":"2i2c","org_slug":"2i2c","date":"2022-08-30","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0501","shared_components":["node-image"]},{"id":"IL-0144","title":{"en":"A systemd security update installed by unattended-upgrades lost the DNS configuration of Ubuntu 18.04 VMs, so AKS kubelets could not resolve registry names and pods failed with ImagePullBackOff","ko":"Ubuntu 18.04 의 systemd 보안 업데이트가 DNS 설정을 날려 AKS 노드의 kubelet 이 레지스트리 이름을 해석하지 못하고 파드가 ImagePullBackoff 에 빠졌다."},"org":"Microsoft Azure","org_slug":"microsoft-azure","date":"2022-08-30","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0144","shared_components":["node-image"]}]