[{"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":["kubelet","dns-resolver"]},{"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":["dns-resolver"]},{"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":["kube-proxy"]}]