Rolling update

As explained in Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

A change technique that updates similar infrastructure resources incrementally, validating each resource before proceeding to the next.

A rolling update changes a group of similar infrastructure resources one by one, testing each resource before continuing. This limits the blast radius of a failed configuration or upgrade. section 10.1.1 section 10.3

Apply the technique as an ordered, validated replacement process:

• Create or configure one replacement resource using the new infrastructure definition. section 10.1.1
• Deploy the application or workload to the replacement resource. section 10.1.1
• Test the resource’s functionality before proceeding. section 10.1.1
• Remove the old resource and repeat the process for the remaining resources. section 10.1.1

Upgrading production servers

A team upgrades DNS and load balancers first, then updates servers individually. When an override script breaks on the first upgraded server, the team fixes and tests it before continuing, keeping the remaining servers unaffected. section 13.2.2

Figure 10.1 Use rolling updates to create each new server, deploy the application, and test its functionality while minimizing disruption to other resources.

Visualize each replacement as a cycle of creating a server, deploying the application, testing functionality, and minimizing disruption to other resources. section 10.1.1

How Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform covers it

How deep it goes

Explains the sequential replacement-and-test workflow and failure isolation, without detailing automation implementation.

Examples

Uses replacement servers, application tests, DNS and load-balancer upgrades, and a broken server override script.

What it assumes

Assumes infrastructure-as-code resources and validation tests, while teaching the rolling replacement sequence from its operational scenario.

What you can do after

Apply incremental infrastructure changes and diagnose failures before they affect the remaining resources.

How it connects

Connects rolling updates with infrastructure as code, refactoring, blue-green deployment, backward compatibility, and roll-forward techniques.

liveBookmanning.com

Read Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Kubernetes in Action, Second EditionThe RollingUpdate strategy is a deployment update strategy that replaces application pods gradually while applying an updated pod template.
• 

  liveBookmanning.com
  Acing the Certified Kubernetes Administrator Exam, Second EditionAn application rollout is the controlled, versioned progression of deploying a new workload or application version through successive revisions.
• 

  liveBookmanning.com
  Amazon Web Services in Action, Third Edition: An in-depth guide to AWSA rolling update replaces instances or software versions incrementally while keeping enough of the existing deployment available to avoid service interruption.
• 

  liveBookmanning.com
  Machine Learning Platform EngineeringA rolling update is a gradual replacement of running application instances with instances of a newer version while maintaining service availability.
• 

  liveBookmanning.com
  Kubernetes for DevelopersA rolling update incrementally replaces instances of an application with a new version while retaining some existing instances during the transition.
• 

  liveBookmanning.com
  Platform Engineering on KubernetesA rolling update replaces running application instances incrementally by starting updated instances and terminating older ones after the replacements are ready.
• 

  liveBookmanning.com
  Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformA rolling update is a deployment technique that incrementally replaces running application instances with a new version while keeping other instances available.

Compare how 8 books explain rolling update →

Related concepts

• Recreate strategycontrasts with · A recreate strategy replaces an application version by stopping all existing instances before starting instances of the new version.
• consumer group rebalancingproduces · Consumer group rebalancing is the redistribution of topic-partition assignments among consumer group members after membership or partition availability changes.
• blue-green deploymentincludes · Blue-green deployment is a release pattern that maintains separate active and replacement environments and switches traffic between them after the replacement is validated.
• Kubernetes Deploymentused by · A Kubernetes Deployment is a declarative API resource that manages the desired state, scaling, and updates of a replicated application workload.
• maxUnavailableconfigured by · maxUnavailable is a Kubernetes rolling-update setting that limits the number of Pods allowed to be unavailable during an update.
• maxSurgeconfigured by · maxSurge is a Kubernetes rolling-update setting that limits the number of additional Pods allowed above the desired replica count.

This explainer was generated by Manning's knowledge graph from the text of Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform. The section links point to the parts of the book it draws on.