anchor.diff:  $ oc rollout history dc/<name> --revision=1
   ----
   
  -For more detailed information about a deployment configuration and its latest deployment:
  +For more detailed information about a deployment configuration and its latest revision:
   
   ----
   $ oc describe dc <name>
  
positive.code:     post: {}
  ----
  <1> How long to wait for a scaling event before giving up. Optional; the default is 120.
  <2> `*maxSurge*` is optional and defaults to `25%`; see below.
  <3> `*maxUnavailable*` is optional and defaults to `25%`; see below.
  <4> `*pre*` and `*post*` are both xref:lifecycle-hooks[lifecycle hooks].
  ====
  
  The Rolling strategy will:
  
  . Execute any `*pre*` lifecycle hook.
  . Scale up the new replication controller based on the surge count.
  . Scale down the old replication controller based on the max unavailable count.
  . Repeat this scaling until the new replication controller has reached the desired
  replica count and the old replication controller has been scaled to zero.
  . Execute any `*post*` lifecycle hook.
  
  [IMPORTANT]
  ====
  When scaling down, the Rolling strategy waits for pods to become ready so it can
  decide whether further scaling would affect availability. If scaled up pods
  never become ready, the deployment will eventually time out and result in a
  deployment failure.
  ====
  
  [IMPORTANT]
  ====
  When executing the `*post*` lifecycle hook, all failures will be ignored
  regardless of the failure policy specified on the hook.
  ====
  
  The `*maxUnavailable*` parameter is the maximum number of pods that can be
  unavailable during the update. The `*maxSurge*` parameter is the maximum number
  of pods that can be scheduled above the original number of pods. Both parameters
  can be set to either a percentage (e.g., `10%`) or an absolute value (e.g.,
  `2`). The default value for both is `25%`.
  
negative.code: [[deployment-hooks-using-the-command-line]]
  ==== Using the Command Line
  
  The `oc set deployment-hook` command can be used to set the deployment hook for
  a deployment configuration. For the example above, you can set the
  pre-deployment hook with the following command:
  
  ----
  $ oc set deployment-hook dc/frontend --pre -c helloworld -e CUSTOM_VAR1=custom_value1 \
    -v data --failure-policy=abort -- /usr/bin/command arg1 arg2
  ----
  
  
  [[deployment-resources]]
  == Deployment Resources
  