deployment-patterns

Standardize production deployment workflows with CI/CD, Docker, and Kubernetes health checks.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill deployment-patterns-llmh333
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployment-patterns
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/deployment-patterns
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill deployment-patterns-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the risk and operational chaos of deploying software by providing production-ready deployment workflows, health checks, and rollback strategies that reduce downtime and failure impact.

Core Features & Use Cases

  • Deployment strategy selection: Choose rolling, blue-green, or canary approaches based on tolerance for risk, downtime, and infrastructure constraints.
  • CI/CD pipeline blueprints: Implement automated test, build, container publishing, and staged deployment (staging/smoke/production) flows using common tooling patterns.
  • Health checks and readiness: Add application and Kubernetes probe guidance (liveness/readiness/startup) to fail fast and avoid routing traffic to unhealthy instances.
  • Production readiness and rollback checklists: Verify environment configuration, monitoring, security headers, and rollback prerequisites before release.

Quick Start

Ask the AI to generate a deployment plan using a canary strategy, with health endpoints, Kubernetes probes, and a rollback checklist for your production release workflow.

Frequently Asked Questions about deployment-patterns

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

FAQPage Schema
How do I choose between rolling, blue-green, and canary deployment strategies?

Deployment strategy selection depends on your tolerance for risk, downtime, and infrastructure constraints. Blue-green swaps traffic instantly, canary releases incrementally shift traffic, and rolling updates gradually replace instances.

What is the best way to structure a CI/CD pipeline for Docker container publishing?

A CI/CD pipeline should use deterministic steps for automated testing, image builds, and container publishing. It must pin Docker base image versions, enforce non-root container execution, and define explicit HEALTHCHECK behavior.

How do I configure Kubernetes liveness and readiness probes for stable traffic routing?

Kubernetes probes prevent routing traffic to unhealthy instances by checking application health. You configure liveness, readiness, and startup probes to fail fast and avoid sending requests to containers that are not ready.

Can I automate rollback procedures for a failed canary deployment?

Yes, you can automate rollback procedures for failed releases. The workflow requires documenting rollback prerequisites and assuming backward-compatible rollout assumptions to safely revert traffic during a failed canary deployment.

What should be included in a production readiness checklist before a release?

A production readiness checklist verifies environment configuration, monitoring, security headers, and rollback prerequisites before release. It ensures staged deployments validate smoke tests and that runtime health checks are fully operational.