Master Kubernetes Deployment Strategies: Rolling Update, Recreate, Blue‑Green & Canary

Kubernetes Deployment Strategies Overview

Kubernetes provides several deployment strategies to control how new versions of containerized applications are rolled out, ensuring minimal downtime and reliable updates. The article walks through Rolling Update, Recreate, Blue‑Green, and Canary strategies, showing when each is appropriate.

Prerequisites

You should have basic experience with Kubernetes, access to a cluster, and the kubectl CLI installed. Familiarity with Linux and YAML syntax is also required.

What Is a Deployment?

A Deployment is a declarative Kubernetes resource that defines the desired state of an application, including the container image, replica count, and update behavior. The Deployment controller reconciles the actual state to match the declared state.

Benefits of Using Deployments

Deployments automate updates, handle pod health monitoring, replace failed pods, and provide a consistent way to manage application lifecycles without manual intervention.

Rolling Update Strategy

Rolling Update is the default strategy. It replaces old pods with new ones gradually, avoiding cluster downtime. Two key parameters fine‑tune the process: maxSurge: Number or percentage of extra pods that can be created during an update (default 25%). maxUnavailable: Number or percentage of pods that may be unavailable during the update (default 25%).

Example rollingupdate.yaml:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: rollingupdate-strategy
  version: nanoserver-1709
spec:
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 2
      maxUnavailable: 1
  selector:
    matchLabels:
      app: web-app-rollingupdate-strategy
      version: nanoserver-1709
  replicas: 3
  template:
    metadata:
      labels:
        app: web-app-rollingupdate-strategy
        version: nanoserver-1709
    spec:
      containers:
      - name: web-app-rollingupdate-strategy
        image: hello-world:nanoserver-1709

Apply the deployment and service:

$ kubectl apply -f rollingupdate.yaml

$ kubectl apply -f service.yaml

Monitor progress with:

$ kubectl rollout status deployment/rollingupdate-strategy