Kubernetes
586 incident problems in Kubernetes environments.
먼저 읽을 가이드
추천 문제
All problems (586)
K8S-1940A mesh route is healthy and one tenant still failsOne tenant still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1960A mesh route is healthy and one tenant still failsOne tenant still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1720A mesh route looks healthy and one tenant still failsOne tenant still fails even though the mesh route looks healthy.KubernetesIntermediate11 minProK8S-1690A NetworkPolicy allows the app path in one namespace and still blocks anotherThe same app path works from one namespace and still fails from another after policy cleanup.KubernetesIntermediate11 minProK8S-1678A NetworkPolicy looks correct and one app path still failsOne namespace-to-namespace app path still fails after labels were standardized.KubernetesIntermediate11 minProK8S-1710A service mesh route looks healthy and one tenant still failsOne tenant still fails after the service mesh route looks healthy.KubernetesIntermediate11 minProK8S-1680A cert-manager Certificate is renamed and one HTTPS path still failsHTTPS still fails on one path after a certificate secret rename and reissue.KubernetesIntermediate12 minProCICD-1679A Helm chart is updated and one rollout still restores the previous replica countA rollout keeps applying the previous replica count even though the desired value was changed in Git.CI/CDIntermediate12 minProK8S-1679A PodDisruptionBudget exists and one drain still blocksA node drain still blocks even though replicas look healthy after a label cleanup.KubernetesIntermediate12 minProK8S-1628A Cilium policy is correct and one DNS path still failsOne DNS path still fails after a policy suffix cleanup.KubernetesIntermediate8 minProK8S-1618A Gateway listener is correct and one route still uses the old hostOne Gateway route still uses the old host match after a host rename.KubernetesIntermediate8 minProK8S-1728A Gateway listener is healthy and one backend still misses trafficA backend still misses traffic after the Gateway listener became healthy.KubernetesIntermediate9 minProK8S-1708A Gateway listener is healthy and one route still misses trafficTraffic still misses one route after the Gateway listener became healthy.KubernetesIntermediate9 minProK8S-1738A Gateway listener is healthy and one route still misses trafficOne route still misses traffic after the Gateway listener is healthy.KubernetesIntermediate9 minProK8S-1748A Gateway listener is healthy and one route still misses trafficOne route still misses traffic after the Gateway listener is healthy.KubernetesIntermediate9 minProK8S-1768A Gateway listener is healthy and one route still misses trafficOne route still misses traffic after the Gateway listener is healthy.KubernetesIntermediate9 minProK8S-1788A Gateway listener is ready and one HTTPRoute still missesOne HTTPRoute still misses traffic after the listener became ready.KubernetesIntermediate9 minProK8S-1758A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway listener became ready.KubernetesIntermediate9 minProK8S-1778A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway listener became ready.KubernetesIntermediate9 minProK8S-1798A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minPro