anchor.diff:  $ oc scale dc/logging-fluentd --replicas=0
   ----
   +
  -Wait until they have properly terminated. This helps prevent loss of data by
  -giving them time to properly flush their current buffer and send any logs they
  -were processing to Elasticsearch.
  +Wait until they have terminated. This helps prevent loss of data by giving them
  +time to properly flush their current buffer and send any logs they were
  +processing to Elasticsearch.
   
   . Scale down your Kibana instances:
   +
  
positive.code: $ oc scale dc/logging-kibana-ops --replicas=0
  ----
  
  . Once your Fluentd and Kibana pods are confirmed to be terminated, you can
  safely scale down the Elasticsearch pods:
  +
  ----
  $ oc scale dc/logging-es-<unique_name> --replicas=0
  
negative.code: $ oc scale dc/logging-es-ops-<unique_name> --replicas=0
  ----
  
  . After confirming your Elasticsearch pods have been terminated, rerun the
  deployer to generate any missing or changed features.
  
  ifdef::openshift-origin[]
  .. link:../../install_config/aggregate_logging.html#deploying-the-efk-stack[Re-deploy
  the EFK Stack]. After the deployer completes, re-attach the persistent volumes
  you were previously using.
  endif::openshift-origin[]
  ifdef::openshift-enterprise[]
  .. Follow the first step in
  link:../../install_config/aggregate_logging.html#deploying-the-efk-stack[Deploying
  the EFK Stack]. After the deployer completes, as a cluster administrator,
  re-attach the persistent volumes you were previously using, then deploy a
  template that is created by the deployer:
  +
  ====
  ----
  