---
title: "Discussion on \"How to Debug a Stuck Kubernetes Rollout with a Hands-On Lab\" | Hashnode"
description: "Discussion on \"How to Debug a Stuck Kubernetes Rollout with a Hands-On Lab\". You update a Deployment, run kubectl rollout status, and wait. The command times out. But when you send a request to the Service, it still answers. So did the update finish? And if it didn't, which Po"
url: "https://hashnode.com/posts/how-to-debug-a-stuck-kubernetes-rollout-with-a-hands-on-lab/6abe3dc913d662f7af15bf03"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to Debug a Stuck Kubernetes Rollout with a Hands-On Lab](https://freecodecamp.org/news/how-to-debug-a-stuck-kubernetes-rollout-with-a-hands-on-lab?utm_source=hashnode&utm_medium=feed)

You update a Deployment, run kubectl rollout status, and wait. The command times out. But when you send a request to the Service, it still answers. So did the update finish? And if it didn't, which Po

Oct 1 · 15 min read · freecodecamp.org  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#devops](https://hashnode.com/tag/devops)
-   [#docker](https://hashnode.com/tag/docker)
-   [#debugging](https://hashnode.com/tag/debugging)

## Written by

[Praneeth Kodumagulla](https://hashnode.com/@praneethhere)

@praneethhere · Chicago, USA

  
[View profile](https://hashnode.com/@praneethhere)

Building secure cloud systems today and intelligent AI systems for tomorrow

I'm Praneeth Kodumagulla, a full-stack platform engineer at HSBC and an independent researcher exploring AI agents and automation. My engineering work spans cloud-native applications, Kubernetes, CI/CD, infrastructure automation, and observability, with a focus on reliable systems in financial services. Alongside that work, I build agent prototypes and study how instructions shape autonomous systems’ behavior. I bring a platform engineer’s perspective to AI: how do we test these systems, understand their failures, and make their behavior more dependable? I share what I learn through hands-on tutorials, reproducible experiments, and practical code.

## Responses 1

Markdown supported · ⌘↵ to post

[Oct 1](https://hashnode.com/posts/how-to-debug-a-stuck-kubernetes-rollout-with-a-hands-on-lab/6abe3dc913d662f7af15bf03/comment/6abe691719ce2918e5eea8cc)

Really thorough methodology, especially separating the client-side watch timeout from the controller's own ProgressDeadlineExceeded, that distinction trips people up constantly. One thing worth asking about the recovery step: reapplying the same healthy spec created a brand new revision each time (2 to 4, 4 to 6, 6 to 8) instead of landing back on an existing one. In a setup where you're triggering an automated rollback off ProgressDeadlineExceeded, does kubectl rollout undo without an explicit --to-revision reliably land on the last genuinely healthy spec, or does it just walk back to the most recent distinct ReplicaSet regardless of whether that one was itself a different failure? Two failures in a row would make that ambiguity matter a lot more than the single-fault case this lab walks through.
