anchor.diff:  ----
   ====
   +
  -Be sure to replace at least `*KIBANA_HOSTNAME*` and `*PUBLIC_MASTER_URL*` with values relevant to your
  -deployment. The available parameters are:
  +Be sure to replace at least `*KIBANA_HOSTNAME*` and `*PUBLIC_MASTER_URL*` with
  +values relevant to your deployment.
  ++
  +The available parameters are:
   +
   [cols="3,7",options="header"]
   |===
  
positive.code: 
  == Overview
  
  OpenShift cluster administrators can aggregate logs and
  enable application developers to view them for a range of OpenShift services
  using the EFK stack, which is a modified version of the
  https://www.elastic.co/videos/introduction-to-the-elk-stack[ELK
  stack]. The EFK stack can be useful for viewing logs aggregated from
  hosts and applications, whether coming from multiple containers or even
  deleted pods.
  
  Three components make up the EFK logging stack:
  
  * https://www.elastic.co/products/elasticsearch[Elasticsearch]: an object store where all logs are stored.
  * http://www.fluentd.org/architecture[Fluentd]: gathers logs from nodes and feeds them to Elasticsearch.
  * https://www.elastic.co/guide/en/kibana/current/introduction.html[Kibana]: a web UI for Elasticsearch.
  
  Once deployed on a cluster, the stack aggregates logs from all nodes and
  projects into Elasticsearch and provides a Kibana UI for users to view
  logs that they have access to: for application developers, logs from
  any project they have permission to view; for cluster-administrators,
  all logs.
  
  This topic shows you how to deploy the stack.
  
  [NOTE]
  ====
  
negative.code: [[logging-node-selector]]
  *Node Selector*
  
  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
  link:../admin_guide/managing_projects.html#using-node-selectors[node selector].
  
  To configure a node selector, edit each deployment configuration and add the
  `*nodeSelector*` parameter to specify the label of the desired nodes:
  