anchor.diff:  *Changing the Scale of Elasticsearch*
   
   If you need to scale up the number of Elasticsearch instances your cluster uses,
  -it is not as simple as scaling up an Elasticsearch deployment configuration. This
  -is due to the nature of persistent volumes and how Elasticsearch is configured
  -to store its data and recover the cluster. Instead, scaling up requires creating a deployment
  -configuration for each Elasticsearch cluster node.
  +it is not as simple as scaling up an Elasticsearch deployment configuration.
  +This is due to the nature of persistent volumes and how Elasticsearch is
  +configured to store its data and recover the cluster. Instead, scaling up
  +requires creating a deployment configuration for each Elasticsearch cluster
  +node.
   
   By far the simplest way to change the scale of Elasticsearch is to
   reinstall the whole deployment. Assuming you have supplied persistent
  
positive.code: $ oc new-app logging-deployer-template --param MODE=reinstall
  ----
  
  If you previously deployed using template parameters rather than a configmap,
  this would be a good time to create a configmap instead for future deployer execution.
  
  If you do not wish to reinstall, for instance because you have made
  customizations that you would like to preserve, then it is possible to
  add new Elasticsearch deployment configurations to the cluster using
  a template supplied by the deployer. This requires a more complicated
  procedure however.
  
  During installation, the deployer
  xref:../install_config/imagestreams_templates.adoc#install-config-imagestreams-templates[creates
  templates] with the Elasticsearch configurations provided to it:
  `logging-es-template` (and `logging-es-ops-template` if the deployer was
  run with `*ENABLE_OPS_CLUSTER=true*`). You can use these for scaling, but
  you need to adjust the size-related parameters in the templates:
  
  [cols="3,7",options="header"]
  |===
  
negative.code: $ chown 1000:1000 /usr/local/es-storage
  ----
  
  Then, use *_/usr/local/es-storage_* as a host-mount as described below.
  Performance under this solution is significantly worse than using actual local
  drives.
  ====
  
  It is possible to use a local disk volume (if available) on each
  