anchor.diff:  
   ====
   
  -== Specifying a custom duration per Project
  +[[specifying-a-custom-duration-per-project]]
  +== Specifying a Custom Duration per Project
   
  -In addition to specifying a global maximum duration for run-once pods, an administrator can add an annotation (`openshift.io/active-deadline-seconds-override`)
  -to a specific project to override the global default.
  +In addition to specifying a global maximum duration for run-once pods, an
  +administrator can add an annotation
  +(`openshift.io/active-deadline-seconds-override`) to a specific project to
  +override the global default.
   
   ====
   
  
positive.code: Note that the value of the override must be specified in string form.
  
  ====
  
  
negative.code: toc::[]
  
  == Overview
  
  {product-title} relies on run-once pods to perform tasks such as
  link:../dev_guide/deployments.html[deploying a pod] or
  link:../dev_guide/builds.html[performing a build]. Run-once pods are pods that
  have a `*RestartPolicy*` of `Never` or `OnFailure`.
  
  The cluster administrator can use the *RunOnceDuration* admission control
  plug-in to force a limit on the time that those run-once pods can be active.
  Once the time limit expires, the cluster will try to actively terminate those
  pods. The main reason to have such a limit is to prevent tasks such as builds to
  run for an excessive amount of time.
  
  [[configuring-the-run-once-duration-plug-in]]
  == Configuring the RunOnceDuration Plug-in
  
  The plug-in configuration should include the default active deadline for
  run-once pods. This deadline will be enforced globally, but can be superseded on
  a per-project basis.
  
  ====
  
  