[{"id":"IL-0098","title":{"en":"After 2i2c moved from ingress-nginx to nginx-ingress, a hub's Ingress took priority over cert-manager's temporary Ingress for the same host, so new hubs could not get TLS certificates","ko":"ingress-nginx 에서 nginx-ingress 로 옮긴 뒤 같은 호스트를 나눠 쓰는 인그레스들의 동작이 바뀌어 cert-manager 가 새 TLS 인증서를 받지 못했다."},"org":"2i2c","org_slug":"2i2c","date":"2026-03-31","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0098","shared_components":["ingress"]},{"id":"IL-0092","title":{"en":"Upgrading ingress-nginx from 1.12.0 to 1.14.3 brought a newer ModSecurity and OWASP Core Rule Set whose false positives blocked HMPPS Auth, so users could not sign in to their applications","ko":"ingress-nginx 를 1.12.0 에서 1.14.3 으로 올리자 새 ModSecurity 와 OWASP Core Rule Set 이 정상 요청을 오탐으로 막아 HMPPS 사용자가 인증하지 못했다."},"org":"UK Ministry of Justice","org_slug":"uk-ministry-of-justice","date":"2026-03-30","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0092","shared_components":["ingress"]},{"id":"IL-0117","title":{"en":"A scheduled maintenance and an ingress upgrade on OpenAI's user-facing clusters caused a networking control plane regression that briefly broke the data plane, and the services that restarted then overwhelmed a backend persistence store with a heavy first-start query","ko":"인그레스 업그레이드가 네트워크 컨트롤 플레인 회귀를 일으켜 데이터 플레인이 잠깐 끊겼고, 한꺼번에 재시작한 서비스들이 백엔드 저장소에 과부하를 일으켜 OpenAI API 오류가 늘었다"},"org":"OpenAI","org_slug":"openai","date":"2024-08-16","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0117","shared_components":["ingress"]},{"id":"IL-0203","title":{"en":"A routine Kubernetes cluster system update made the AWS Load Balancer Controller fail, so new pods were never registered with the ALB and Honeycomb's EU1 ingest and UI went down once the last old pods were replaced","ko":"클러스터 시스템 업데이트 뒤 AWS Load Balancer Controller 가 실패해 새 파드가 ALB 에 등록되지 않았고, Honeycomb EU1 의 수집과 UI 가 11분 동안 멈췄다"},"org":"Honeycomb","org_slug":"honeycomb","date":"2024-04-09","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0203","shared_components":["ingress"]},{"id":"IL-0180","title":{"en":"A GKE control plane auto-upgrade from 1.22 to 1.23 removed the v1beta1 Ingress and ValidatingWebhookConfiguration APIs that Istio 1.7.4 still used, and Istio stopped working in production","ko":"GKE 컨트롤 플레인이 1.22 에서 1.23 으로 자동 업그레이드되면서 v1beta1 API 를 쓰던 Istio 1.7.4 가 제대로 동작하지 않았다"},"org":"Sunwoo Park","org_slug":"sunwoo-park","date":"2023-05-18","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0180","shared_components":["admission-webhook"]},{"id":"IL-0060","title":{"en":"Kubernetes 1.24 upgrade removed the master node label that Calico route reflectors selected on, dropping all pod routes and taking Reddit down for 314 minutes","ko":"쿠버네티스 1.24 업그레이드로 node-role.kubernetes.io/master 레이블이 사라지자 이 레이블에 기대던 Calico 라우트 리플렉터가 동작을 멈춰 레거시 클러스터의 네트워크가 모두 끊기고 Reddit 이 314분 동안 멈췄다"},"org":"Reddit","org_slug":"reddit","date":"2023-03-14","severity":"unknown","root_cause":"upgrade-breaking-change","url":"https://benchlet.com/incidentlib/app/cases/IL-0060","shared_components":["admission-webhook"]}]