CKA
955 incident response problems that help with CKA prep.
먼저 읽을 가이드
추천 문제
All problems (955)
K8S-1647An HPA metric is visible and one autoscaler still reads zeroOne HPA still reads zero after a metric rename.KubernetesBeginner7 minFreeK8S-1657An HPA metric is visible and one autoscaler still reads zeroOne HPA still reads zero after a metric rename.KubernetesBeginner7 minFreeK8S-1667An HPA metric is visible and one autoscaler still reads zeroOne HPA still reads zero after a metric rename.KubernetesBeginner7 minFreeK8S-1626An HPA target is visible and one scale rule still reads the old metric type fieldThe metric is present, but one autoscaler still uses the earlier target type.KubernetesBeginner7 minFreeK8S-1613An Ingress change is correct and one path still returns 404One Ingress path still returns 404 after annotation cleanup.KubernetesBeginner7 minFreeK8S-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-005A declarative manifest problem where deployment failsA scenario that narrows down the root cause, centered on checking prerequisite resources and the deployment order, in the situation of a declarative manifest problem where deployment fails because the Namespace is missing.KubernetesBeginner14 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-013Node draining takes longer than expectedA scenario that narrows down the root cause, centered on designing the balance between high availability and operational convenience, in the situation of node draining taking longer than expected because of a PodDisruptionBudget.KubernetesAdvanced25 minProK8S-1198Stateful workload appears healthy until rescheduleA workload seems safe in steady state, and community examples suggest using local cache for speed. After eviction or node loss, recovery exposes that one critical path was never durable.KubernetesAdvanced25 minProK8S-1193Node stays NotReadyA node image refresh followed public upgrade guidance. New nodes join, but one networking daemonset fails to initialize and the nodes never reach a stable Ready state.KubernetesAdvanced26 minProK8S-015After adding a NetworkPolicy, only the observability agent cannot communicateA situation where the main services are fine but only the monitoring agent is blocked, making incident diagnosis harder.KubernetesAdvanced27 minProK8S-018GPU workloads stay Pending even though the cluster autoscaler is onGPU workloads stay Pending even though the cluster autoscaler is on is a hands-on troubleshooting drill. A situation where the autoscaler is working but the workload waits because of a special node-group condition. Kubernetes Scheduling and Capacity needs to be checked by narr...KubernetesAdvanced29 minProK8S-014An overly aggressive liveness probe keeps restarting even healthy PodsAn overly aggressive liveness probe keeps restarting even healthy Pods is a hands-on troubleshooting drill. A situation where the liveness criteria become too tight during periods of high application load. Kubernetes Config and Rollouts needs to be checked by narrowing scope,...KubernetesIntermediate19 minPro