anchor.diff:  
   . Create deployment:
   
  -    $ kubectl create -f templates/app-rolling.yaml
  +    $ kubectl create -f templates/app-rolling.yaml --record
       deployment "app-rolling" created
  ++
  +Once again, `--record` ensures that the command initiating this deployment is recorded. This is useful when the application has gone through a few updates and you need to correlate a version with the command.
  ++
  +. Get the history of deployments:
  +
  +    $ kubectl rollout history deployment/app-rolling
  +    deployments "app-rolling"
  +    REVISION  CHANGE-CAUSE
  +    1         kubectl create --filename=templates/app-rolling.yaml --record=true
   
   . Expose service:
   
  -    $ kubectl expose deployment/app-rolling --port=8080 --name=app-rolling --type=LoadBalancer
  +    $ kubectl expose deployment/app-rolling --port=80 --name=app-rolling --type=LoadBalancer
       service "app-rolling" exposed
   
   . Get service detail:
  
positive.code: 
  Let's look at these two deployment strategies.
  
  === Recreate strategy
  
  All existing pods are killed before the new ones are created. The configuration file looks like:
  
  
negative.code:     $ kubectl set image deployment/app-rolling app-rolling=arungupta/app-upgrade:v2
      deployment "app-rolling" image updated
  
  . Status of the pods is updated:
  
      $ kubectl get -w pods
      NAME                           READY     STATUS    RESTARTS   AGE
  