anchor.diff:  
   == Overview
   
  -A *HorizontalPodAutoscaler* object specifies how the system should automatically
  -increase or decrease the scale of a *ReplicationController* or *DeploymentConfig*,
  -based on metrics collected from the pods that belong to that *ReplicationController*
  -or *DeploymentConfig*.
  +A horizontal pod autoscaler, defined by a `*HorizontalPodAutoscaler*` object,
  +specifies how the system should automatically increase or decrease the scale of
  +a replication controller or deployment configuration, based on metrics collected
  +from the pods that belong to that replication controller or deployment
  +configuration.
   
  +ifdef::openshift-enterprise[]
   [NOTE]
   ====
  -Horizontal Pod Autoscaling is currently a Tech Preview feature.
  +Horizontal pod autoscaling is currently a Technology Preview feature.
   ====
  +endif::[]
   
   ifdef::openshift-origin,openshift-enterprise[]
  +[[req-for-using-hpas]]
   == Requirements for Using Horizontal Pod Autoscalers
   
  -In order to use *HorizontalPodAutoscalers*, your cluster admin must have
  -link:../install_config/cluster_metrics.html[properly configured cluster metrics].
  +In order to use horizontal pod autoscalers, your cluster administrator must have
  +link:../install_config/cluster_metrics.html[properly configured cluster
  +metrics].
   endif::openshift-origin,openshift-enterprise[]
   
  -== Metrics Supported
  +[[hpa-supported-metrics]]
  +== Supported Metrics
   
  -The following describes the metrics supported by *HorizontalPodAutoscalers*:
  +The following metrics are supported by horizontal pod autoscalers:
   
   .Metrics
   [cols="3a,8a",options="header"]
  
positive.code: Min pods:                       1
  Max pods:                       10
  ----
  
  ====
  
  
negative.code: |Percentage of the link:../dev_guide/compute_resources.html#cpu-requests[requested CPU]
  |===
  
  [[hpa-autoscaling]]
  == Autoscaling
  
  After a horizontal pod autoscaler is created, it begins attempting to query
  Heapster for metrics on the pods. It may take one to two minutes before Heapster
  obtains the initial metrics.
  
  After metrics are available in Heapster, the horizontal pod autoscaler computes
  the ratio of the current metric utilization with the desired metric utilization,
  and scales up or down accordingly. The scaling will occur at a regular interval,
  but it may take one to two minutes before metrics make their way into Heapster.
  
  For replication controllers, this scaling corresponds directly to the replicas
  of the replication controller. For deployment configurations, this will scale
  the latest deployment, or, if no deployment is present, the replication
  controller template in the deployment configuration. Note that scaling will
  occur if the latest deployment is marked as `Complete`.
  
  [[creating-a-hpa]]
  == Creating a Horizontal Pod Autoscaler
  
  To create a horizontal pod autoscaler, first define it in a file. For example:
  
  .Horizontal Pod Autoscaler Object Definition
  ====
  [source,yaml,options="nowrap"]
  ----
  