Kubernetes Ingress and Traffic
114 incident problems about Kubernetes Ingress and Traffic. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (114)
K8S-1644An Ingress host is added and one path still failsOne path still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1673An Ingress host is added and one path still failsOne Ingress path still fails after a service port name cleanup.KubernetesBeginner7 minFreeK8S-1634An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1654An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1664An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1694An Ingress host is added and one route still failsOne route still fails after an Ingress host update.KubernetesBeginner7 minFreeK8S-1624An Ingress TLS secret is ready and one host still failsOne host still fails TLS after an Ingress hostname update.KubernetesBeginner7 minFreeK8S-002Analyzing a service failure where the Pod is Running but receives no trafficA scenario for step-by-step checking of Service, Endpoint, readiness probe, and selector mismatch possibilities.KubernetesIntermediate22 minProK8S-009Only certain APIs return 404 due to an Ingress path-rewrite rule mismatchCovers a path-rewrite problem where health checks pass but only real user requests fail.KubernetesIntermediate24 minProK8S-017Readiness time spikes sharply after a service-mesh sidecar is attachedA situation where the proxy initialization, rather than the application itself, becomes the bottleneck and lengthens startup.KubernetesIntermediate24 minProK8S-081Readiness passes but Envoy sidecar cannot reach the control plane after a trust bundle splitThe app container is healthy, yet traffic still fails because the sidecar lost trust in the mesh control plane after the certificate bundle changed unevenly.KubernetesAdvanced21 minProK8S-069Cross-node gRPC calls failIntra-node traffic is clean, but larger cross-node requests hang because one node pool uses a smaller effective MTU than the other path expects.KubernetesAdvanced24 minProK8S-023Admission webhook blocks only one namespace pathAdmission webhook blocks only one namespace path is a hands-on troubleshooting drill. Most workloads apply normally, but a webhook policy rejects a specific namespace because labels and defaults diverge. Kubernetes Ingress and Traffic needs to be checked by narrowing scope, re...KubernetesAdvanced28 minProK8S-080Ingress controller leader election lease stayed in the old namespace after a migrationThe new controller deploys cleanly, yet only one replica ever reconciles because the election objects still point at the namespace pattern from the previous release.KubernetesAdvanced18 minProK8S-100Ingress leader election looks healthy but one class still routes nowhereThe controller pods are up, yet routes for one ingress class remain empty because the controller cannot write the status fields other components depend on.KubernetesAdvanced18 minProK8S-052Readiness probe fails only after service mesh sidecar intercepts the health portThe container answers correctly on its native port, but the probe fails because the sidecar path or redirected port does not match the probe expectation.KubernetesAdvanced24 minProK8S-056kube-proxy keeps sending traffic to a deleted backendEndpoints changed correctly, but some nodes still route to a dead backend because stale load-balancing state was not reconciled as expected.KubernetesAdvanced26 minProK8S-022Service endpoint count drops during rolling updateService endpoint count drops (Rollout Stuck) is a hands-on troubleshooting drill. Pods are healthy one by one, but the endpoint pool shrinks too far during rollout and causes short traffic gaps. Kubernetes Ingress and Traffic needs to be checked by narrowing scope, recent chan...KubernetesIntermediate23 minProK8S-1700A Cilium policy is correct and one DNS path still failsA DNS path still fails from one workload even after the Cilium policy was corrected.KubernetesIntermediate11 minProK8S-1790A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minPro