CKA
955 incident response problems that help with CKA prep.
먼저 읽을 가이드
추천 문제
All problems (955)
K8S-031Slow-starting JVM pod loopsLiveness and readiness probes look reasonable for a steady-state service, but the application restarts repeatedly during warmup because it never gets a dedicated startup window.KubernetesIntermediate21 minProK8S-1190HPA never scalesPublic HPA examples were applied and the object looks valid. The workload never scales because the actual metrics path is missing or unreadable.KubernetesIntermediate22 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-040Node eviction startsApplication storage looks healthy on the persistent volume, but a temporary working directory on the node root filesystem silently fills and triggers eviction pressure.KubernetesIntermediate24 minProK8S-1008A ServiceAccount token audience is correct for the main API callA ServiceAccount token audience is correct for the main API call focuses on kubernetes-access-and-policy and asks the reader to isolate Auth and Session Failure. 실무에서는 auth-and-session-failure 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesIntermediate28 minProK8S-1620A PVC expansion succeeds and one pod still reports no spaceOne pod still reports no space after PVC expansion.KubernetesIntermediate10 minProK8S-1630NodeLocal DNS is healthy and one node still resolves stale namesOne node still resolves stale names after a CoreDNS upstream change.KubernetesIntermediate10 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 minProK8S-1810A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1820A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1850A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1880A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1910A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1920A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1950A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1970A mesh route is healthy and one client still failsOne client still fails even though the mesh route is healthy.KubernetesIntermediate11 minProK8S-1730A mesh route is healthy and one tenant still failsOne tenant still fails after the mesh route looks healthy.KubernetesIntermediate11 minProK8S-1740A mesh route is healthy and one tenant still failsOne tenant still fails even though the mesh route looks healthy.KubernetesIntermediate11 minProK8S-1750A mesh route is healthy and one tenant still failsOne tenant still fails even though the mesh route looks healthy.KubernetesIntermediate11 minPro