Service Discovery
91 incident problems about Service Discovery. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (91)
K8S-1901A Service selector is corrected and one endpoint is still missingOne endpoint is still missing after the Service selector fix.KubernetesBeginner6 minFreeK8S-1911A Service selector is corrected and one endpoint is still missingOne endpoint is still missing after the Service selector fix.KubernetesBeginner6 minFreeK8S-1811A Service selector is fixed and one endpoint is still missingOne endpoint is still missing after the Service selector fix.KubernetesBeginner6 minFreeK8S-1731A Service selector is fixed and one endpoint list is still emptyA Service still has no endpoints after the selector fix.KubernetesBeginner6 minFreeK8S-1681A Service selector is fixed and one endpoint set is still emptyA Service still has no endpoints after the selector was corrected.KubernetesBeginner6 minFreeK8S-1691A Service selector is fixed and one endpoint set is still emptyA Service still has no endpoints after the selector was corrected.KubernetesBeginner6 minFreeK8S-1711A Service selector is fixed and one endpoint slice is still emptyAn endpoint slice is still empty after the Service selector was fixed.KubernetesBeginner6 minFreeK8S-1741A Service selector is fixed and one endpoint slice is still emptyA Service still has no endpoints after the selector fix.KubernetesBeginner6 minFreeK8S-1761A Service selector is fixed and one endpoint slice is still emptyA Service still has no endpoints after the selector fix.KubernetesBeginner6 minFreeK8S-1781A Service selector is fixed and one pod still stays outOne pod still stays out after the Service selector fix.KubernetesBeginner6 minFreeK8S-1199kubectl port-forward works but ingress still failsA team confirms the app with kubectl port-forward and assumes ingress must be fine. The actual failure sits earlier in the edge-hostname or path-rewrite chain.KubernetesIntermediate18 minProNETWORK-1577An Unbound override is fixed and one resolver still answers the old zoneOne resolver still answers the old zone after Unbound override fixes.NetworkAdvanced9 minProNETWORK-1602An EVPN import policy is fixed and one leaf still learns the wrong routeOne leaf still learns the wrong route after an EVPN policy fix.NetworkAdvanced10 minProK8S-1581A Cilium endpoint restore works and one node still denies trafficOne node still denies traffic after endpoint restore and label normalization.KubernetesAdvanced11 minProK8S-1591A Cilium node restore completes and one service still routes wrongOne node still routes wrong after Cilium restore and CIDR recycling.KubernetesAdvanced11 minProK8S-1561A Cilium kube-proxy replacement rollout finishes and one node still sends traffic to the old backendOne node still sends requests to an old backend after kube-proxy replacement rollout.KubernetesAdvanced12 minProK8S-1521A Cilium node upgrade finishes and one service path still dropsTraffic drops only from one node after a high-churn service rollout on Cilium.KubernetesAdvanced12 minProK8S-1541A Cilium node upgrade finishes and one service path still dropsTraffic drops only from one node after a service rollout on Cilium.KubernetesAdvanced12 minProK8S-1551A Cilium policy rollout finishes and one node still bypasses egress rulesOne node bypasses egress policy after identity translation rules change.KubernetesAdvanced12 minProK8S-1501A Cilium policy rollout looks correct and one namespace still drops east-west trafficCross-cluster service traffic fails only from one node pool after a Cilium peering update.KubernetesAdvanced12 minPro