How deeply does Kubernetes for Developers cover blue-green deployment?

Explains deployment, testing, traffic switching, validation, rollback, costs, and tooling, but not detailed configuration steps.

Blue-green deployment

As explained in Kubernetes for Developers

A blue/green strategy is a rollout technique that runs old and new application versions side by side and switches traffic between them.

Blue-green deployment runs the existing and new application versions side by side. After the new version is fully deployed and tested, traffic switches to it; if problems appear, traffic can switch back immediately. section 4.2.3

A blue-green rollout trades temporary resource cost for fast, controlled releases:

Keeps only one version live for users after cutover, preserving a consistent experience. section 4.2.3
Completes cutovers and rollbacks within seconds when both environments remain ready. section 4.2.3
Temporarily doubles compute usage because both versions stay scaled up during validation. section 4.2.3
May route internal users or a percentage of external traffic to the new version before full cutover through canary analysis. section 4.2.3
Requires additional tooling or manual process because Kubernetes Deployments do not directly support blue-green rollouts. section 4.2.3

A controlled production switch

Deploy the new version alongside the old one, test it, and direct the Service to the new Deployment. Keep the old version available while the new version is evaluated, then remove it after validation or switch traffic back if a problem appears. section 4.2.3

How Kubernetes for Developers covers it

liveBook manning.com

Read Kubernetes for Developers on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Platform Engineering on KubernetesA blue/green deployment runs an existing version and a replacement version separately, allowing traffic to be switched between them after validating the replacement.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformA blue-green deployment is a release pattern that maintains separate old and new infrastructure environments and switches service traffic between them.
liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsA red-green deployment is a deployment strategy that runs two application versions in parallel and shifts traffic incrementally from the active version to the new version without visible downtime.
liveBook manning.com

Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformBlue-green deployment is a release technique that runs old and new application versions in parallel and switches traffic between them.

Compare how 5 books explain blue-green deployment →

Related concepts

rolling updatekind of · A rolling update is a deployment or upgrade technique that updates or replaces instances or resources incrementally rather than all at once, allowing the rest of the system to continue operating during the change.
canary deploymentalternative to · A canary deployment is a release strategy that exposes a change to a limited portion of users, traffic, or infrastructure before expanding it more broadly.
load balanceruses · A load balancer is a hardware or software component that distributes incoming network traffic or requests among multiple destinations, such as servers or service instances.

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.