anchor.diff:  By far the simplest way to change the scale of Elasticsearch is to
   reinstall the whole deployment. Assuming you have supplied persistent
   storage for the deployment, this should not be very disruptive. Simply
  -re-run the deployer with the updated `*es-cluster-size*` configuration
  -value and the `*MODE=reinstall*` template parameter. For example:
  +re-run the deployer with the updated `es-cluster-size` configuration
  +value and the `MODE=reinstall` template parameter. For example:
   
   ----
   $ oc edit configmap logging-deployer
  
positive.code: 
  To configure Searchguard to ignore the extra header:
  
  . Scale down all Fluentd pods
  . Scale down Elasticsearch after the Fluentd pods have terminated
  . Add `searchguard.http.xforwardedfor.header: DUMMY` to the Elasticsearch
  configuration section
  +
  ====
  ----
  oc edit configmap/logging-elasticsearch <1>
  ----
  <1> This approach requires that Elasticsearch's configs are within a configmap
  ====
  +
  . Scale Elasticsearch back up
  . Scale up all Fluentd pods
  
  [[sending-logs-to-an-external-elasticsearch-instance]]
  == Sending Logs to an External Elasticsearch Instance
  
  Fluentd sends logs to the value of the `*ES_HOST*`, `*ES_PORT*`, `*OPS_HOST*`,
  and `*OPS_PORT*` environment variables of the Elasticsearch deployment
  configuration. The application logs are directed to the `*ES_HOST*` destination,
  and operations logs to `*OPS_HOST*`.
  
  [NOTE]
  ====
  
negative.code: dedicated region within your cluster, using a
  xref:../admin_guide/managing_projects.adoc#using-node-selectors[node selector].
  
  To configure a node selector, specify the `es-nodeselector` configuration
  option at deployment. This applies to all Elasticsearch deployments; if you need
  to individualize the node selectors, you must manually edit each deployment
  configuration after deployment.
  