deployment-patterns

Blue-green deployment for Dockerized applications involves maintaining two identical production environments, routing traffic to the new version after validation, and keeping the old version for immediate rollback. This Skill provides concrete configuration examples and health checks to automate this CI/CD pattern safely.

Rolling deployments update instances incrementally, blue-green switches traffic between two identical environments, and canary releases route a small percentage of traffic to the new version first. This Skill outlines these deployment strategies with example scenarios to help standardize your safe releases.

Configuring Kubernetes liveness and readiness probes requires defining HTTP endpoints that verify your service is running and ready to accept traffic. This Skill provides health check configurations and production readiness checklists to ensure your containerized services meet staging and production standards.

A production-ready CI/CD pipeline should include automated validation, Docker multi-stage builds, health probes, and documented rollback procedures. This Skill offers sample GitHub Actions workflows and deployment automation guidelines to streamline these processes across staging and production environments.

Feature flags allow toggling functionality without redeploying, while rollback procedures revert the entire deployment to a previous state. This Skill covers both approaches, helping you implement feature flags and concrete rollback procedures to handle deployment failures safely.

Yes, this Skill operates without external dependencies, providing standardized deployment workflows, Docker best practices, and production readiness checklists. It applies directly to teams implementing CI/CD pipelines and containerized services across staging and production environments.