How deeply does Kubernetes in Action, Second Edition cover kubectl rollout restart?

Defines Pod deletion and replacement, then distinguishes gradual RollingUpdate behavior from simultaneous Recreate behavior.

Kubectl rollout restart

As explained in Kubernetes in Action, Second Edition

kubectl rollout restart is a kubectl command that recreates the pods managed by a workload resource.

kubectl rollout restart recreates all Pods managed by a Deployment without changing its application version. It deletes and replaces the Pods using the Deployment’s configured update strategy. section 15.2.6

Restart a Deployment

Run kubectl rollout restart for the target Deployment when its Pods need restarting. With RollingUpdate, Kubernetes recreates Pods gradually to maintain service availability. With Recreate, it deletes and recreates all Pods simultaneously. section 15.2.6

The restart preserves the Deployment’s configured rollout behavior:

RollingUpdate gradually replaces Pods while maintaining service availability. section 15.2.6
Recreate deletes all Pods before recreating them simultaneously. section 15.2.6

How Kubernetes in Action, Second Edition covers it

Cover of Kubernetes in Action, Second Edition

liveBook manning.com

Read Kubernetes in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Road to Kuberneteskubectl rollout restart is a kubectl command that triggers a new rollout of a Kubernetes workload without deleting the workload resource.

Compare how 2 books explain kubectl rollout restart →

Related concepts

Kubernetes Deploymentuses · A Kubernetes Deployment is a declarative API resource that manages the desired state, scaling, and updates of a replicated application workload.
Kubernetes controlleruses · A Kubernetes controller is a control-loop component that observes resource state and takes action to move actual state toward desired state.
rolling updateuses · 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.

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