Cluster Networking and Service Discovery
35 incident problems about Cluster Networking and Service Discovery. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (35)
K8S-381A NetworkPolicy permits the application path while node-local DNS forwarding now uses a different source identity than the rule expected during a staged decommissionApp traffic is allowed, yet name resolution fails because the helper path no longer matches policy assumptions. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.KubernetesIntermediate16 minProK8S-124An ingress rewrite rule strips the trailing slash from the websocket path and only interactive sessions fail while health checks stay greenThe service looks healthy through normal probes, yet upgraded connections hit a subtly different path contract.KubernetesIntermediate16 minProK8S-300A headless Service gives every pod address while the client library still randomizes from a stale cached subset after scale-down during a failover rehearsalService discovery is accurate and the client keeps dialing endpoints that no longer exist. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate17 minProK8S-258A stubDomain forwards internal names correctly while negative caching at node-local DNS hides newly created services during a failover rehearsalThe forwarding chain is right, but one layer remembers failure longer than the service lifecycle. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate17 minProK8S-180Cluster DNS is correct while one client runtime caches the first answer indefinitely during a failover rehearsalThe service discovery layer updates and the consuming library behaves as if nothing changed. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate17 minProK8S-142The service mesh sidecar starts after the application, and the startup probe passes once before all outbound traffic begins failingInitialization timing hid the networking dependency because the first health check ran before the sidecar took control.KubernetesIntermediate17 minProK8S-479A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate18 minProK8S-483A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate18 minProK8S-497A NetworkPolicy permits the application pathA NetworkPolicy permits the application path focuses on cluster-networking-and-service-discovery and asks the reader to isolate DNS Resolution Failure. 실무에서는 dns-resolution-failure 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesIntermediate18 minProK8S-499A NetworkPolicy permits the application pathA NetworkPolicy permits the application path focuses on cluster-networking-and-service-discovery and asks the reader to isolate DNS Resolution Failure. 실무에서는 dns-resolution-failure 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesIntermediate18 minProK8S-501A NetworkPolicy permits the application pathA NetworkPolicy permits the application path focuses on cluster-networking-and-service-discovery and asks the reader to isolate DNS Resolution Failure. 실무에서는 dns-resolution-failure 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesIntermediate18 minProK8S-168A sidecar takes over networking after the application already passed its first startup probe during a failover rehearsalHealth looks good once, but the final runtime path is not the one the probe validated. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.KubernetesIntermediate18 minProK8S-484A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate19 minProK8S-539A gateway API route is admitted (404 and Rewrite Mismatch)A gateway API route is admitted (404 and Rewrite Mismatch) focuses on cluster-networking-and-service-discovery and asks the reader to isolate 404 and Rewrite Mismatch in NGINX. 실무에서는 404-and-rewrite-mismatch 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶...KubernetesIntermediate19 minProK8S-557A NetworkPolicy permits the application pathA NetworkPolicy permits the application path focuses on cluster-networking-and-service-discovery and asks the reader to isolate DNS Resolution Failure. 실무에서는 dns-resolution-failure 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesIntermediate19 minPro