rollout-check

Analyze Kubernetes deployment rollout status, pod readiness, events, and HPA state.

3|1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/indrasvat/claude-code-skills --skill rollout-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rollout-check
Source: https://github.com/indrasvat/claude-code-skills/tree/main/skills/rollout-check
Command: npx skills add https://github.com/indrasvat/claude-code-skills --skill rollout-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rollout health checks ensure Kubernetes deployments are fully rolled out, healthy, and stable after changes by validating rollout status, pod readiness, events, resource usage, HPA posture, and container logs.

Core Features & Use Cases

  • Rollout status and progress checks against deployment/<name> to confirm completion or identify stalled rollouts.
  • Pod readiness and health assessment, including crash loops and not-ready states, with focused log collection for problematic pods.
  • Events and resource usage aggregation to surface warnings, errors, and potential bottlenecks after deployments.
  • HPA visibility for the deployment, showing current and desired replicas and recent scaling activity.
  • Use Case: After pushing a new image, run a rollout-health check to verify all pods are Ready, no warnings, and the deployment has stabilized.

Quick Start

Provide the deployment name (and optionally --namespace and --context) to run a rollout health check.

Frequently Asked Questions about rollout-check

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

FAQPage Schema
How do I verify Kubernetes deployment rollout health after pushing a new image?

To verify Kubernetes rollout health, you need to check rollout status, pod readiness, and recent events. This Skill automates that validation by analyzing deployment completion, crash loops, and warnings to ensure post-rollout stability.

How do I check pod readiness and diagnose crash loops in a Kubernetes namespace?

Checking pod readiness in Kubernetes involves identifying not-ready states and collecting logs from problematic pods. This Skill assesses pod health, detects crash loops, and aggregates resource usage to surface potential deployment bottlenecks.

Can I check Kubernetes HPA state and scaling activity for a specific deployment?

Yes, you can check Kubernetes HPA state for a deployment. This Skill provides HPA visibility by showing current and desired replicas alongside recent scaling activity to ensure your deployment scales correctly after changes.

Do I need kubectl access to run a Kubernetes rollout health check?

Yes, kubectl access is required to run a Kubernetes rollout health check. You must provide the deployment name and have kubectl access configured to the target cluster, namespace, and context to validate status and resource usage.

What is the best way to diagnose a stalled Kubernetes rollout across environments?

Diagnosing a stalled Kubernetes rollout requires checking deployment progress, pod events, and container logs. This Skill runs kubectl-based checks against the deployment to identify stalled rollouts and surface warnings or errors across namespaces.

Why does my Kubernetes deployment show not-ready pods after a rollout?

Kubernetes deployments show not-ready pods when containers fail to start or hit crash loops. This Skill diagnoses these failures by aggregating cluster events, checking pod readiness, and collecting focused logs from problematic pods.