[{"id":"IL-0463","title":{"en":"Secure Connect connectors timed out after a GKE control plane upgrade left Harness's internal load balancer unreachable","ko":"Harness Secure Connect 의 내부 로드 밸런서에 닿을 수 없게 되어 Secure Connect 를 쓰는 git 커넥터 검사와 CI 파이프라인이 실패했다"},"org":"Harness","org_slug":"harness","date":"2026-05-12","severity":"unknown","root_cause":"cloud-provider","url":"https://benchlet.com/incidentlib/app/cases/IL-0463","shared_components":["gke-control-plane"]},{"id":"IL-0542","title":{"en":"Twingate authentication and authorization requests failed at higher rates after traffic moved onto a smaller GKE cluster","ko":"Twingate 의 인증과 인가 요청 일부에서 약 30분 동안 오류율이 올라갔다"},"org":"Twingate","org_slug":"twingate","date":"2025-03-21","severity":"unknown","root_cause":"cloud-provider","url":"https://benchlet.com/incidentlib/app/cases/IL-0542","shared_components":["gke-control-plane"]},{"id":"IL-0084","title":{"en":"Packet drops on a bare metal provider's vSwitch forced Namespace to rebuild its fra3 region and left global capacity short, and the next day slow NVMe writes on a control plane node drove the Kubernetes API server to very high CPU","ko":"베어메탈 업체 vSwitch 의 패킷 드롭으로 Namespace 의 fra3 리전이 빠져 전 세계 용량이 모자랐고, 다음 날에는 컨트롤 플레인 노드의 느린 NVMe 쓰기로 쿠버네티스 API 서버 CPU 가 치솟아 zrh1 이 멈췄다."},"org":"Namespace","org_slug":"namespace","date":"2024-10-22","severity":"unknown","root_cause":"cloud-provider","url":"https://benchlet.com/incidentlib/app/cases/IL-0084","shared_components":["kube-apiserver"]},{"id":"IL-0014","title":{"en":"A GKE upgrade to a withdrawn version stalled on slow drains and a stuck node pool, then broke an ingress and confused the HPA","ko":"GKE 를 1.12.5-gke.10 으로 올리는 중 노드 풀 업그레이드가 멈추고 인그레스와 HPA 가 망가졌다"},"org":"loveholidays","org_slug":"loveholidays","date":"2019-03-19","severity":"unknown","root_cause":"cloud-provider","url":"https://benchlet.com/incidentlib/app/cases/IL-0014","shared_components":["gke-control-plane"]},{"id":"IL-0469","title":{"en":"The managed Azure Kubernetes API server for the data100 hub stopped answering, so the stopped hub pod was not recreated","ko":"Azure 관리형 쿠버네티스의 API 서버가 응답하지 않아 data100 허브 파드가 다시 만들어지지 않았다"},"org":"UC Berkeley","org_slug":"uc-berkeley","date":"2019-02-25","severity":"unknown","root_cause":"cloud-provider","url":"https://benchlet.com/incidentlib/app/cases/IL-0469","shared_components":["kube-apiserver"]}]