CKA
955 incident response problems that help with CKA prep.
먼저 읽을 가이드
추천 문제
All problems (955)
K8S-1231A StatefulSet stays PendingA stateful workload scales one replica further and the new pod never schedules despite spare cluster capacity.KubernetesAdvanced20 minProK8S-025Cross-namespace DNS lookup works in debug pod but not app podA quick debug shell resolves the name, while the workload container fails because search domains and runtime image differ.KubernetesIntermediate20 minProK8S-079Namespace deletion hangsMost resources are gone, but deletion never completes because one finalizer must call an API service that is no longer reachable in the cluster.KubernetesAdvanced20 minProK8S-032PodDisruptionBudget blocks maintenance drain on a low-replica deploymentThe node drain command hangs even though workloads seem healthy, because a tight disruption budget and replica count leave no legal eviction path.KubernetesIntermediate20 minProK8S-1226Pods stay Pending after scale-outA stateful workload scales during an incident and new pods remain Pending even though several nodes appear idle.KubernetesAdvanced20 minProK8S-1213PVC is bound but the pod still misses rollout windowsA stateful workload gets its PVC but still appears hung every time it starts.KubernetesAdvanced20 minProK8S-074Admission latency spikesThe webhook service exists, but requests from one path stall because the backing Deployment lost zonal coverage and the API server keeps timing out on remote retries.KubernetesAdvanced21 minProK8S-099API server audit logs show the patch but the controller cache never sees itThe update reaches the API, yet the controller behaves as if nothing changed because its watch stream state drifted and the resync never caught up.KubernetesAdvanced22 minProK8S-1210CoreDNS stays degraded after node changesA new self-managed worker pool is added and CoreDNS remains degraded even though the managed pool looks healthy.KubernetesIntermediate22 minProK8S-083HPA scales on CPU but the true bottleneck is a single-threaded queue consumer partition assignmentAutoscaling appears to help, yet throughput never rises because the workload's shard or partition ownership keeps all useful work pinned to one replica.KubernetesAdvanced22 minProK8S-1203Ingress health looks good but one path still 404sA rewrite snippet copied from community answers works for one route. Another path still 404s because an upstream edge layer is also transforming the path unexpectedly.KubernetesAdvanced22 minProK8S-070metrics-server loses the aggregated API after the front-proxy CA bundle driftsThe pod is running, but autoscaling and kubectl top fail because the aggregated API trust chain no longer matches the API server front-proxy configuration.KubernetesAdvanced23 minProK8S-1183Ingress NGINX returns 400 on WebSocket pathA public ingress-nginx snippet was copied into production. Browser requests work until the WebSocket path crosses an extra proxy boundary.KubernetesIntermediate24 minProK8S-061Topology spread and zone taints keep replicas pending after a node drainCapacity still exists in the cluster, but the workload cannot recover because spread rules and taints together eliminate every legal placement choice.KubernetesAdvanced24 minProK8S-065One node rejects new podsThe node still reports in, but admission and management paths fail because kubelet trust renewal broke when time drift invalidated the rotation flow.KubernetesAdvanced25 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-037TopologySpreadConstraints leave replicas pending although one node has roomThe cluster has enough raw CPU and memory, but zone spread requirements and maxSkew prevent any legal placement for the remaining replicas.KubernetesAdvanced26 minProK8S-1121A topology spread rule looks balanced (Rollout Stuck)A topology spread rule looks balanced (Rollout Stuck) focuses on kubernetes-workload-reliability and asks the reader to isolate Rollout Stuck. 실무에서는 Rollout Stuck 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesAdvanced31 minProK8S-1584A cert-manager issuer switch is correct and one order still waitsOne cert-manager order remains pending after issuer switch.KubernetesIntermediate8 minProK8S-1606A CoreDNS rewrite fix lands and one namespace still resolves old namesOne namespace still resolves old names after a CoreDNS rewrite fix.KubernetesIntermediate8 minPro