anchor.diff:  
   Let's verify.
   
  -=== Create canary
  +==== Create canary
   
   . Deploy `v1` version of Deployment:
   
  
positive.code: 
  Canary deployment allows to deploy a new version of the application in production by slowly rolling out the change to a small subset of users before rolling it out to everybody.
  
  This can be achieved in Kubernetes using Service, Deployment and Labels.
  
  === Deployment and Service definition
  
  Let's look at version `v1` of the Deployment:
  
  
negative.code: +
  Note that we are explicitly specifying the label `name=app` in the query to only pick the pods that are specified in the service definition at `templates/app-service.yaml`. There are two pods from `v1` version and 2 pods from `v2` version. Accessing this service will have 50% response from `v1` version and the other 50% from `v2` version.
  
  ==== Scale canary
  
  The number of pods to be included from `v1` version and `v2` version can now be indepently scaled using the two Deployments.
  
  