anchor.diff:  into a container in general, but in particular it can be used to synchronize
   local source code into a running application framework. For frameworks that
   support hot deployment when files change, this enables an extremely responsive
  -"code, save, debug" workflow with source on the developer's machine using the their
  +"code -> save -> debug" workflow with source on the developer's machine using the their
   IDE of choice, while the application runs in the cloud with access to any
   service it depends on, such as databases.
   
  
positive.code: [[ocp-33-cluster-longevity]]
  === Cluster Longevity
  
  This release adds the following improvements to cluster longevity, helping it
  remain stable under frequent and constant use. This includes taking advantage of
  Kubernetes workload priority and eviction policies, an ability to idle and
  unidle workloads, increasing the number of pods per node and node per cluster,
  and helping developers find the right persistent storage for their deployments
  needs.
  
  [[ocp-33-pod-eviction]]
  ==== Pod Eviction
  
negative.code: one for high availability) in the cluster to become edge routers or they can
  just run additional pods on the HAProxy nodes.
  
  For example, a platform administrator can run additional pods that are
  ipfailover pods. A pool of available Ingress IPs are specified that are routable
  to the nodes in the cluster and resolvable externally via the corporate DNS.
  This pool of IP addresses are served out to developers who want to use a port other
  