⌂ Home

Deployment Strategies

Interactive guide to recreate, rolling update, blue-green, and canary release strategies.

Release strategy is about balancing simplicity, user impact, rollback speed, and operational risk.

Core Model

Understand the Concept First

Recreate

Stop old Pods, then start new ones. Simple, but causes downtime.

Rolling update

Gradually replace old Pods with new Pods while keeping the app available.

Blue-green and canary

Traffic-control strategies that provide stronger safety for risky changes.

Lifecycle Flow

Decide how much downtime, risk, and duplicate capacity you can tolerate.

Choose recreate, rolling, blue-green, or canary.

Update Pods or switch traffic using the selected approach.

Validate health, metrics, and user impact before completing the rollout.

There is no universally best strategy. The right choice depends on cost, risk, traffic patterns, and rollback needs.

YAML and Commands

RollingUpdate Strategy

strategy:
  type: RollingUpdate

Blue-Green Idea

Blue environment + Green environment + traffic switch

Decision Guide

Strategy	Strength	Tradeoff
Recreate	Very simple	Downtime during switch
RollingUpdate	Good availability during rollout	Rollback is controlled but not instant
Blue-Green	Fast cutover and rollback	Requires duplicate environment capacity
Canary	Limits blast radius of risky changes	Needs more routing and observability maturity

Rolling updates are the default for a reason, but blue-green and canary are often better when release risk is high.

Use It Well

General web apps

Rolling updates are usually the most practical starting point.

High-risk releases

Use canary to expose only a portion of users first.

Fast rollback needs

Blue-green works well when you need instant cutover reversal.