In the previous chapter, we learned that the Kubernetes Deployment object distinguishes itself from the ReplicaSet object in that it adds rolling updates and rollbacks on top of the latter's functionality. Let's use our web component to demonstrate this. Evidently, we will have to modify the manifest or description of the deployment for the web component.
We will use the same deployment definition as in the previous section, with one important difference – we will have five replicas of the web component running. The following definition can also be found in the ~/fod/ch16/web-deploy-rolling-v1.yaml file:
apiVersion: apps/v1kind: Deploymentmetadata: name: webspec: replicas: 5 selector: matchLabels: app: pets service: web template: ...
