Rollout Stuck
384 incident problems that show up as “Rollout Stuck”.
먼저 읽을 가이드
추천 문제
All problems (384)
K8S-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 minProCICD-053OCI Helm chart publish succeeds but cluster still pulls the previous chartThe registry receives the new chart artifact, yet the deployment job keeps resolving the previous digest because the chart reference and version bump were not updated together.CI/CDIntermediate20 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 minProCICD-105Rollback restores the app chart but not the migration job image and the database contract stays ahead of the codeA release rollback appears complete, yet application errors continue because the migration runner image remained on the newer schema contract.CI/CDAdvanced20 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 minProCICD-081Approval workflow promotes the wrong artifactThe review step is followed correctly, but the production deployment still uses the wrong image because the artifact reference is re-evaluated after a newer build already exists.CI/CDAdvanced21 minProCICD-055CodeBuild local cache reuses stale base layer after package repository changedBuild time looks great, but the produced image quietly carries an older package baseline because local Docker layer cache survives a repository-side base image update.CI/CDIntermediate21 minProLINUX-083LUKS volume unlock works manually but the early boot keyscript path is missing from initramfsThe passphrase and device are valid, yet unattended boot fails because the initramfs never included the helper needed to unlock the volume at the correct stage.LinuxAdvanced21 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-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 minProLINUX-810An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate23 minProLINUX-073mdadm auto-assembly picks the wrong member order after an initramfs still references stale metadataThe disks are present, but recovery stays risky because the boot environment is assembling the array from outdated metadata assumptions.LinuxAdvanced23 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 minProCICD-022Canary deploy passes health checks but fails background jobsCanary deploy passes health checks but fails background jobs is a hands-on troubleshooting drill. The web process looks healthy while the worker image lags behind and starts processing incompatible payloads. GitHub Actions Workflows needs to be checked by narrowing scope, rece...CI/CDIntermediate24 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-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 minProLINUX-1170An application writes Unicode filenames correctlyAn application writes Unicode filenames correctly focuses on linux-performance-and-observability and asks the reader to isolate Rollout Stuck. 실무에서는 linux-performance-and-observability 문제를 볼 때 서비스 로그만 보지 말고 inode, 파일시스템 여유, 포트 점유, systemd 상태, 최근 패키지 변경까지 같이 확인해야 원인을 빨리 좁힐 수 있습니다.LinuxIntermediate29 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 minProCICD-136A coverage gate compares against a stale default-branch baseline after the repository renamed its main branchNew tests are good enough, but the gate keeps failing because it still measures against a branch that no longer receives changes.CI/CDIntermediate14 minPro