Recreate strategy

As explained in Acing the Certified Kubernetes Administrator Exam, Second Edition

A recreate strategy terminates all old workload instances before starting instances of the new version.

A recreate strategy stops every pod from the old ReplicaSet before starting pods from the new version. The application therefore experiences downtime, but the rollout is fast and avoids running multiple application versions simultaneously. section 5.1.2

Use this strategy when:

• The application cannot support multiple versions running together, such as when database locks create compatibility problems. section 5.1.2
• The fastest rollout is preferred and planned downtime is acceptable. section 5.1.2
• Set spec.strategy.type to Recreate and remove rollingUpdate, maxSurge, and maxUnavailable fields. section 5.1.2

Configure and verify a recreate rollout

Edit the Deployment with kubectl edit deploy apache, change the strategy type from RollingUpdate to Recreate, and remove the rolling-update fields. Use kubectl explain deploy.spec.strategy when checking valid YAML fields. section 5.1.2

Figure 5.9 The update process for a Deployment when deleting and creating new replicas

Follow the update sequence showing old replicas being deleted before new replicas are created. section 5.1.2

How Acing the Certified Kubernetes Administrator Exam, Second Edition covers it

How deep it goes

Explains pod replacement order, YAML changes, speed, and downtime without detailing controller internals.

Examples

Uses kubectl edit deploy apache, strategy YAML fields, kubectl explain, and an update-process diagram.

What it assumes

Assumes familiarity with Deployments, ReplicaSets, pods, and Deployment YAML.

What you can do after

Operate/configure a Deployment with Recreate and verify its rollout sequence using kubectl.

How it connects

Connects Deployments, ReplicaSets, rolling updates, database locks, and downtime.

liveBookmanning.com

Read Acing the Certified Kubernetes Administrator Exam, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Kubernetes in Action, Second EditionThe Recreate strategy is a deployment update strategy that replaces all existing application pods at once before creating the updated pods.
• 

  liveBookmanning.com
  Kubernetes for DevelopersA re-create strategy replaces a deployed workload by stopping all instances of the old version before starting instances of the new version.

Compare how 3 books explain Recreate strategy →

Related concepts

• rolling updatecontrasts with · 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.
• update strategykind of · An update strategy is a policy that determines how a Kubernetes workload replaces running instances when its configuration changes.
• Kubernetes controllerconfigured by · A Kubernetes controller is a control-loop component that observes resource state and takes action to move actual state toward desired state.
• blue-green deploymentcontrasts with · Blue-green deployment is a release pattern that maintains separate active and replacement environments and switches traffic between them after the replacement is validated.

This explainer was generated by Manning's knowledge graph from the text of Acing the Certified Kubernetes Administrator Exam, Second Edition. The section links point to the parts of the book it draws on.