Kubernetes Cookbook - Second Edition

How it works...

Rolling-update works on the units of the ReplicaSet in a Deployment. The effect is to create a new ReplicaSet to replace the old one. Then, the new ReplicaSet is scaling up to meet the desired numbers, while the old ReplicaSet is scaling down to terminate all the Pods in it. The Pods in the new ReplicaSet are attached to the original labels. Therefore, if any service exposes this Deployment, it will take over the newly created Pods directly.

An experienced Kubernetes user may know that the resource ReplicationController can be rolling-update as well. So, what are the differences of rolling-update between ReplicationController and deployment? The scaling processing uses the combination of ReplicationController and a client ...