Kubernetes
586 incident problems in Kubernetes environments.
먼저 읽을 가이드
추천 문제
All problems (586)
K8S-1808A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1818A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1828A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1838A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1858A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1868A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1878A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1928A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1938A Gateway listener is ready and one route still missesOne route still misses traffic after the Gateway fix.KubernetesIntermediate9 minProK8S-1718A Gateway route attaches and one backend still misses trafficOne backend still misses traffic after Gateway attachment.KubernetesIntermediate9 minProK8S-1629A Gateway route is accepted and one backend still failsOne Gateway backend still fails after moving the service to another namespace.KubernetesIntermediate9 minProK8S-1688A Gateway route is accepted and one backend still failsA Gateway route is healthy, yet one backend path still fails after a service moved namespaces.KubernetesIntermediate9 minProK8S-1640A Gateway route is attached and one backend still failsOne Gateway backend still fails after moving a service.KubernetesIntermediate9 minProK8S-1660A Gateway route is attached and one backend still failsOne Gateway backend still fails after moving a service.KubernetesIntermediate9 minProK8S-1670A Gateway route is attached and one backend still failsOne Gateway backend still fails after moving a service.KubernetesIntermediate9 minProK8S-1676A Gateway route is attached and one backend still failsA Gateway backend still fails after the service moved to another namespace.KubernetesIntermediate9 minProK8S-1698A Gateway route is attached and one backend still failsA Gateway route is healthy but one backend path still fails after migration.KubernetesIntermediate9 minProK8S-1619A NetworkPolicy allow rule exists and one pod still times outOne pod still times out after a namespace label update.KubernetesIntermediate9 minProK8S-1689A PodDisruptionBudget exists and one drain still blocksA node drain still blocks after the rollout labels were standardized.KubernetesIntermediate9 minProK8S-1699A PodDisruptionBudget exists and one drain still blocksA node drain still blocks after rollout labels were cleaned up.KubernetesIntermediate9 minPro