anchor.diff:  ----
   ====
   
  -You can see the UI by visiting the site specified at the '*KIBANA_HOSTNAME*'
  +You can see the UI by visiting the site specified at the `*KIBANA_HOSTNAME*`
   variable.
   
   See the https://www.elastic.co/guide/en/kibana/4.1/discover.html[Kibana
  
positive.code: ====
  
  If any Kibana pods are live, endpoints will be listed. If they are not, check
  the state of the Kibana pods and deployment.
  
  The second possible issue may be caused if the route for accessing the Kibana
  service is masked. This can happen if you perform a test deployment in one
  
negative.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.
  
  == Pre-deployment Configuration
  
  Deploying the EFK stack requires:
  
  * A *logging-deployer* secret
  * A *logging-deployer* service account with access to the secret and creation privileges
  * Sufficient volumes for Elasticsearch cluster storage
  * A router deployment for serving cluster-defined routes
  
  