Recreate strategy
A recreate strategy replaces an application version by stopping all existing instances before starting instances of the new version.
Kubernetes in Action, Second Edition
The Recreate strategy is a deployment update strategy that replaces all existing application pods at once before creating the updated pods.
- How it is used
- Replaces application pods when old and new versions cannot coexist and brief downtime is acceptable.
- How deep it goes
- Walks through manifest configuration and a three-pod replacement, including pod and ReplicaSet observations; identifies no Recreate tuning options.
- Examples
- Uses a three-replica image upgrade from version 0.5 to 0.6, with pod and ReplicaSet status listings.
- What you can do after
- Operate/configure it by setting `spec.strategy.type` to `Recreate` and changing the Pod template to trigger replacement.
Read how Kubernetes in Action, Second Edition explains Recreate strategy →
Acing the Certified Kubernetes Administrator Exam, Second Edition
A recreate strategy terminates all old workload instances before starting instances of the new version.
- How it is used
- Deploys versions that cannot safely run concurrently while accepting application downtime.
- 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 you can do after
- Operate/configure a Deployment with Recreate and verify its rollout sequence using kubectl.
Kubernetes for Developers
A re-create strategy replaces a deployed workload by stopping all instances of the old version before starting instances of the new version.
- How it is used
- Uses direct replacement for development, staging, or services that cannot run two versions simultaneously.
- How deep it goes
- Explains Pod replacement, downtime, capacity, compatibility, and configuration, but stops short of detailed rollout internals.
- Examples
- Uses development, staging, legacy single-instance services, and a Kubernetes strategy field as concrete examples.
- What you can do after
- Operate/configure a Kubernetes Deployment with the Recreate strategy and judge its downtime and capacity tradeoffs.
Read how Kubernetes for Developers explains 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.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.