The title of this chapter is A Load-Balanced Order Processing Microservice Using Docker and Azure Kubernetes Service. In fact, you've already seen this since the worker pods were picking up items from the queue based on which were available. However, let's see if we can engineer a more dramatic demonstration of what that actually means. Let's go into the dashboard and delete one of the pods; select the ellipsis to the right-hand side of a pod and delete it:
Once you've deleted the pod, you should (almost instantly) notice the screen change to look something like this:
As you can see, as soon as Kubernetes realizes that you have killed one of the pods, it instantly compensates by starting a new one! How did it know to do this? Well, in our deployment.yaml file, we had set the replicas to be 2. To prove this, let's increase the replicas...