anchor.diff:  $ oc rollout pause deployments/<name>
   ----
   
  -Currently, Deployments do not support `ImageChange` triggers. A generic
  -triggering mechanism has been proposed upstream, but it is unknown if and when
  -it may be accepted. Eventually, a {product-title}-specific mechanism could be
  -implemented to layer on top of Deployments, but it would be more desirable for
  -it to exist as part of the Kubernetes core.
  -
   [discrete]
   ==== Lifecycle hooks
   
  -Deployments do not support any lifecycle hooks.
  +Deployments do not yet support any lifecycle hooks.
   
   [discrete]
   ==== Custom strategies
   
  -Deployments do not yet support user-specified Custom deployment
  +Deployments do not support user-specified Custom deployment
   strategies yet.
  -
  -[discrete]
  -==== Canary deployments
  -
  -Deployments do not yet run canaries as part of a new rollout.
  -
  -[discrete]
  -==== Test deployments
  -
  -Deployments do not support running test tracks.
   
   [id="delpoyments-specific-features-{context}"]
   == Deployments-specific features
  
positive.code: [id="deployments-comparing-deploymentconfigs-{context}"]
  = Comparing Deployments and DeploymentConfigs
  
  Because deployment configurations existed in {product-title} prior to
  deployments being added in Kubernetes 1.2, the latter object type naturally
  diverges slightly from the former. The long-term goal in {product-title} is to reach
  full feature parity in Deployments and switch to using them as a
  single object type that provides fine-grained management over applications.
  
  Deployments are supported to ensure upstream projects and examples that use the
  new object type can run smoothly on {product-title}. Given the current feature
  set of Deployments, you might want to use them instead of deployment
  configurations in {product-title} if you do not plan to use any of the following
  in particular:
  
  - Image streams
  - Lifecycle hooks
  - Custom deployment strategies
  
  The following sections go into more details on the differences between the two
  object types to further help you decide when you might want to use Kubernetes
  deployments over deployment configurations.
  
  [id="delpoymentconfigs-specific-features-{context}"]
  == DeploymentConfigs-specific features
  
negative.code: 
  Deployments can be paused at any point in time, meaning you can also
  pause ongoing rollouts. On the other hand, you cannot pause deployer pods
  currently, so if you try to pause a DeploymentConfig in the middle of a
  rollout, the deployer process will not be affected and will continue until it
  finishes.
  