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:     app-rolling-1683885671-k8xn9   0/1       Terminating   0         5m
      app-rolling-4154020364-vlb4b   1/1       Running   0         2s
  +
  The output shows how a new pod is created, then an old one is terminated, then a new pod is created and so on.
  +
  . Access the application again:
  
      $ curl http://a2ea9ce7dbd9f11e791f402037f18a54-1449990061.eu-central-1.elb.amazonaws.com:8080
      Howdy World!
  +
  The output now shows `v2` version of the image is being used.
  
  == Rollback
  
  More details about 
  
  == Delete resources
  
  Delete resources created in this chapter:
  
      kubectl delete deployment/app-recreate svc/app-recreate deployment/app-rolling svc/app-rolling
  
negative.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:
  
  