anchor.diff:  ----
   ====
   
  +[NOTE]
  +====
  +Allowing the pods to mount host volumes as above usually requires
  +adding the `aggregated-logging-elasticsearch` service account to
  +the privileged SCC, similarly as for Fluentd above.
  +====
  +
   You can use any volume type, such as
   link:../install_config/persistent_storage/persistent_storage_nfs.html[NFS].
   
   *Node Selector*
   
  -Because Elasticsearch can use a lot resources, all members of a cluster should
  +Because Elasticsearch can use a lot of resources, all members of a cluster should
   have low latency network connections to each other. Ensure this by directing the
   instances to dedicated nodes, or a dedicated region within your cluster, using a
   node selector.
  
positive.code: ----
  ====
  +
  Then, ensure the *logging-deployer* can edit the service. The following example
  uses the `logging` project. Be sure to use the project created above in the
  following example:
  +
  ====
  ----
  $ oc policy add-role-to-user edit \
            system:serviceaccount:logging:logging-deployer
  ----
  ====
  
  == Deploying the EFK Stack
  
  The EFK stack is deployed link:../dev_guide/templates.html[using a template].
  Doing so ensures all future project configurations will feature the EFK stack.
  The default repository and branch of the template are set to origin/master.
  Change these settings to suit your own instance if desired.
  
  ifdef::openshift-enterprise[]
  The template is available on install, and can be created with the following
  command:
  
  ----
  $ oc create -f /usr/share/ansible/openshift-ansible/roles/openshift_examples/files/examples/infrastructure-templates/enterprise/logging-deployer.yaml
  ----
  endif::openshift-enterprise[]
  
  ifdef::openshift-origin[]
  The template can be created with the following command:
  
  ----
  $ oc create -f https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_examples/files/examples/infrastructure-templates/origin/logging-deployer.yaml
  ----
  endif::openshift-origin[]
  
  
  
  [IMPORTANT]
  ====
  The OpenShift Authentication Proxy (*openshift-auth-proxy*) depends on a *node*
  base image, which is intended to be the DockerHub Node.js base image. Defining
  standard templates also depends on a Node.js image called *node*, which will be
  used instead of the intended image, causing the build to fail. To resolve this,
  delete the older *node* image:
  
  ----
  $ oc delete is/node -n openshift
  ----
  ====
  
  After defining any builds, they should restart. If they do not, you can manually
  restart each component:
  
  ----
  $ oc start-build <component>
  ----
  
  Once the builds have successfully completed, the image streams will be populated
  and ready for deployment. However, you must first specify the `*IDEX_PREFIX*`
  parameter with the registry location.
  
  . Run the deployer, specifying the host on which kibana will run, the amount of
  instances of Elasticsearch to deploy, and the master URL where browsers will be
  directed to when authenticating to OpenShift. Be sure to replace the
  `*KIBANA_HOSTNAME*` and `*PUBLIC_MASTER_URL*` to values relevant to your
  deployment:
  +
  ====
  ----
  
negative.code: |*_server-tls.json_*
  |JSON TLS options to override the Kibana server defaults. Refer to
  https://nodejs.org/api/tls.html#tls_tls_connect_options_callback[Node.JS] docs
  for available options.
  
  |*_ca.crt_*
  |A certificate for a CA that will be used to sign all certificates generated by
  