anchor.diff:  $ 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:
  +. Once confirming your Fluentd and Kibana pods have been terminated, scale down
  +the Elasticsearch pods:
   +
   ----
   $ oc scale dc/logging-es-<unique_name> --replicas=0
  
positive.code: [[manual-upgrading-efk-logging-stack]]
  == Upgrading the EFK Logging Stack
  
  If you have previously link:../../install_config/aggregate_logging.html[deployed
  the EFK logging stack] and want to upgrade to the latest logging component
  images, you must take the following steps to safely upgrade with minimal
  disruption to your log data.
  
  [NOTE]
  ====
  
negative.code: 1.1 to 1.2.
  endif::[]
  ifdef::openshift-enterprise[]
  3.1 to 3.2, or are applying an asynchronous update to 3.2. These steps pull
  the latest 3.2 logging images.
  endif::[]
  ====
  
  . Ensure you are working in the project where the EFK stack was previously
  deployed. For example, if the project is named *logging*:
  +
  ----
  $ oc project logging
  