deployment-rollout-debug

Diagnose Kubernetes Deployment rollout failures via kubectl inspection.

225|28|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/scitix/siclaw --skill deployment-rollout-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-rollout-debug
Source: https://github.com/scitix/siclaw/tree/main/skills/core/deployment-rollout-debug
Command: npx skills add https://github.com/scitix/siclaw --skill deployment-rollout-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and understand why Kubernetes Deployment rollouts are failing, stuck, or not progressing as expected, preventing downtime and ensuring smooth application updates.

Core Features & Use Cases

  • Rollout Status Check: Verifies the current state of a Deployment rollout.
  • ReplicaSet Analysis: Examines the old and new ReplicaSets to pinpoint issues with pod creation or readiness.
  • Pod Health Diagnosis: Identifies problems with new pods, such as Pending, CrashLoopBackOff, or ImagePullBackOff states, and suggests further debugging skills.
  • Use Case: When a new version of your application fails to deploy and the rollout is stuck, this Skill will investigate the Deployment, its ReplicaSets, and the status of new pods to identify the root cause, such as a failing readiness probe or an image pull error.

Quick Start

Use the deployment-rollout-debug skill to diagnose why the deployment named 'my-app' in the 'production' namespace is not rolling out successfully.

Frequently Asked Questions about deployment-rollout-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a stuck Kubernetes deployment rollout?

Debug a stuck Kubernetes deployment rollout by checking the rollout status, analyzing old and new ReplicaSets for replica mismatches, and inspecting new pod health to identify root causes like failing readiness probes.

Why does my Kubernetes deployment show ProgressDeadlineExceeded?

Kubernetes deployment shows ProgressDeadlineExceeded when new pods fail to become ready within the configured deadline. Diagnose this by examining ReplicaSet rollout status and new pod states such as CrashLoopBackOff or ImagePullBackOff.

How do I diagnose Kubernetes replica mismatches during a rollout?

Diagnose Kubernetes replica mismatches during a rollout by analyzing the current Deployment rollout status and comparing the old and new ReplicaSets to pinpoint why pod creation or readiness is failing.

Do I need kubectl to troubleshoot Kubernetes deployment failures?

Yes, you need kubectl to troubleshoot Kubernetes deployment failures because it interacts directly with the Kubernetes API to inspect deployment rollout status, ReplicaSets, and pod health for root cause analysis.

What causes new pods to fail during a Kubernetes rollout update?

New pods fail during a Kubernetes rollout update due to issues like Pending states, CrashLoopBackOff, or ImagePullBackOff. Analyze pod health and ReplicaSet status to identify the specific failure preventing readiness.

Can I find out why my production application deployment is not progressing?

Find out why a production application deployment is not progressing by investigating the Deployment, its ReplicaSets, and new pod health to identify root causes such as image pull errors or failing readiness probes.