CKA
955 incident response problems that help with CKA prep.
먼저 읽을 가이드
추천 문제
All problems (955)
K8S-1380A PodDisruptionBudget looks safe and node drains still stallA drain or upgrade stalls after autoscaling and rollout settings were changed independently across teams.KubernetesIntermediate12 minProK8S-1383A Prometheus adapter exposes an external metric and the HPA never scalesA Prometheus adapter exposes an external metric and the HPA never scales focuses on runtime-configuration and asks the reader to isolate the key signal in grafana. Autoscaling adapters fail quietly when a single ownership label disappears bet...KubernetesIntermediate12 minProK8S-1401A Prometheus Operator upgrade looks healthy and one ServiceMonitor stops...A Prometheus Operator upgrade looks healthy and one ServiceMonitor stops... focuses on Observability Pipeline and asks the reader to isolate the key signal in Prometheus. Prometheus scraping outages after chart upgrades o...KubernetesIntermediate12 minProK8S-1350A Prometheus scrape target keeps flapping (servicemonitor-still-targeted-old-port-name)A Prometheus scrape target keeps flapping (servicemonitor-still-targeted-old... focuses on runtime-configuration and asks the reader to isolate the key signal in grafana. Monitoring often binds to names, not just numbers, and chart cleanups can qui...KubernetesIntermediate12 minProK8S-1362A PrometheusRule loads fine and never firesA monitoring refactor splits rules into cleaner groups and later one alert never triggers during a known outage simulation.KubernetesIntermediate12 minProK8S-1372A PrometheusRule loads without errors and never firesA rules refactor cleans up files and later one alert fails to trigger during a known outage simulation.KubernetesIntermediate12 minProK8S-1364A ServiceMonitor exists and Prometheus scrapes nothingA monitoring manifest cleanup centralizes resources and later one application's metrics vanish despite healthy endpoints.KubernetesIntermediate12 minProK8S-1374A ServiceMonitor exists and Prometheus scrapes nothingA monitoring cleanup centralizes manifests and later one application's metrics vanish despite healthy endpoints.KubernetesIntermediate12 minProK8S-1398A Velero restore finishes and one application never comes upA Velero restore finishes and one application never comes up focuses on cluster-maintenance and asks the reader to isolate the key signal in Kubernetes. Restore plugins can quietly alter object content even when restore status looks successful.KubernetesIntermediate12 minProK8S-1404An HTTP01 challenge solver succeeds on IPv4 and fails globallyAn HTTP01 challenge solver succeeds on IPv4 and fails globally focuses on ingress-routing and asks the reader to isolate the key signal in Kubernetes. Dual-stack rollouts can turn a healthy solver pod into a globally failing valida...KubernetesIntermediate12 minProK8S-1381Metrics Server stays ready and the HPA still shows unknownMetrics Server stays ready and the HPA still shows unknown focuses on runtime-configuration and asks the reader to isolate the key signal in Kubernetes. Autoscaling failures often come from address selection drift between components rather...KubernetesIntermediate12 minProK8S-1340A fresh cluster passes smoke tests and later loses alertingA fresh cluster passes smoke tests and later loses alerting focuses on Deployment Governance and asks the reader to isolate the key signal in Kubernetes. Copied platform examples can carry stale label contracts long after the chart has ev...KubernetesIntermediate13 minProK8S-1346A Grafana Agent DaemonSet scrapes node metrics and one node is blankA relabel refactor centralizes monitoring configs and later only one node class disappears from dashboards while scrape targets remain up.KubernetesIntermediate13 minProK8S-1336A pod resolves services on old nodes and times out on fresh nodesA DNS service migration completes and later only pods on newly added nodes see timeouts or stale resolution results.KubernetesIntermediate13 minProK8S-1324A PodDisruptionBudget blocks every node drainA PodDisruptionBudget blocks every node drain focuses on cluster-maintenance and asks the reader to isolate the key signal in Kubernetes. Terminating is not the same as absent from the budget calculation.KubernetesIntermediate13 minProK8S-1302A postStart hook was used as a startup gate and traffic arrives too earlyA team hides bootstrap steps inside a lifecycle hook and later sees early requests fail despite no pod crash.KubernetesIntermediate13 minProK8S-1352A Prometheus scrape target stays downA monitoring refactor centralizes manifests and later one application's metrics vanish despite healthy endpoints and valid PodMonitor syntax.KubernetesIntermediate13 minProK8S-1342A PrometheusRule appears loaded and no alerts fireA monitoring refactor splits rule groups for clarity and later one alert never fires even during a known outage simulation.KubernetesIntermediate13 minProK8S-1358A service mesh sidecar rollout appears safe and readiness flapsA sidecar injection rollout is enabled and later pods begin failing readiness despite healthy application logs.KubernetesIntermediate13 minProK8S-1332A ServiceMonitor appears valid and Prometheus still scrapes nothingA ServiceMonitor appears valid and Prometheus still scrapes nothing focuses on runtime-configuration and asks the reader to isolate the key signal in Kubernetes. Prometheus can miss perfectly valid monitor objects if they moved outside the...KubernetesIntermediate13 minPro