anchor.diff:  
   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 deployment configuration in the middle of a
  +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.
  
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: ==== Proportional scaling
  
  Because the Deployment controller is the sole source of truth for the sizes of
  new and old ReplicaSets owned by a Deployment, it is able to scale ongoing
  rollouts. Additional replicas are distributed proportionally based on the size
  of each ReplicaSet.
  
  DeploymentConfigs cannot be scaled when a rollout is ongoing because the
  DeploymentConfig controller will end up having issues with the deployer
  process about the size of the new ReplicationController.
  
  [discrete]
  