Deployments
A Deployment provides declarative updates for Pods and ReplicaSets.
You describe your desired state in a Deployment, and the Deployment Controller's job is to make the current state match the desired state. You declare your hopes and dreams, and it's Kubernetes' job to make them come true.
Why Deleting a Pod Doesn't Feel Like a Deletion
Remember when we had you delete a pod, only to see that a new pod was created in its place? It's kinda like chopping heads off of a hydra.
That's because the desired state described in our Deployment says we want 2 pods running at all times. When we delete one, the Deployment Controller sees that the current state doesn't match the desired state, so it creates a new pod to make them match again.
Assignment
Take a look at the YAML file for your current deployment in the CLI:
kubectl get deployment synergychat-web -o yaml
Edit the deployment and change the number of replicas from 2 to 10:
kubectl edit deployment synergychat-web
Make sure you've got 10 pods running:
kubectl get pod
Keep using kubectl get pod to check on your pods until all 10 are in a "ready" state. Once they are, run:
kubectl proxy
Run and submit the CLI tests.