deployment-patterns

Design zero-downtime Kubernetes deployments with rollout strategies and health probes.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/jsamuelsen11/claude-config --skill deployment-patterns-jsamuelsen11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/jsamuelsen11/claude-config/tree/main/plugins/ccfg-kubernetes/skills/deployment-patterns
Command: npx skills add https://github.com/jsamuelsen11/claude-config --skill deployment-patterns-jsamuelsen11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying Kubernetes workloads without downtime by coordinating rollout strategies, health probes, and graceful shutdowns.

Core Features & Use Cases

  • RollingUpdate strategies with maxSurge and maxUnavailable to minimize user-visible downtime.
  • Health probes, readiness checks, startup probes, and graceful preStop hooks to ensure safe rollouts.
  • Progressive delivery approaches (blue/green, canary) and PDBs to manage risk and reliability.

Quick Start

Configure deployments to use rolling updates, health probes, and graceful shutdowns to achieve zero-downtime releases.

Frequently Asked Questions about deployment-patterns

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

FAQPage Schema
How do I achieve zero-downtime Kubernetes deployments?

Zero-downtime Kubernetes deployments coordinate rollout strategies, health probes, and graceful shutdowns to prevent user-visible downtime. You configure rolling updates, readiness checks, and preStop hooks to ensure safe rollouts.

What is the best way to configure RollingUpdate maxSurge and maxUnavailable?

RollingUpdate strategies use maxSurge and maxUnavailable parameters to control how many new pods are created and old pods are terminated. This minimizes user-visible downtime by gradually replacing instances during a rollout.

When do I need startup probes and graceful preStop hooks?

Startup probes and graceful preStop hooks are needed when applications require extra time to initialize or terminate. They ensure safe rollouts by preventing premature traffic routing and abrupt connection drops.

Does this approach support blue/green and canary progressive delivery?

Yes, progressive delivery approaches like blue/green and canary are supported to manage risk and reliability. These strategies work alongside Pod Disruption Budgets to control rollout speed and maintain availability.

How do I ensure safe rollback mechanisms during a failed rollout?

Safe rollback mechanisms are ensured by combining health probes, readiness checks, and disruption budgets. If a rollout fails, these coordinated safeguards automatically halt the deployment and revert to a stable state.