anchor.diff:      Howdy World!
   +
   The output now shows `v2` version of the image is being used.
  -+
  -. Delete resources:
  -
  -    kubectl delete deployment/app-rolling svc/app-rolling
   
   == 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
  
positive.code: 
  Note: There is a `kubectl rolling-update` command but it is applicable only to Replica Set. The update from this command was driven on the client-side. It is strongly recommended to do rolling update using Deployment as the updates are now on the server-side.
  
  Updating an application requires to replace all the existing pods with new pods that use a different version of the image. `.spec.strategy` in the Deployment configuration can be used to define strategy used to replace the old pods with the new ones. This key can take two values:
  
  . `Recreate`
  
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:
  
  