anchor.diff:  ----
   ====
   
  +You may wish to create a route to reach Kibana externally:
  +
  +====
  +----
  +$ oc expose service/kibana --hostname=fqdn.example.com
  +----
  +====
  +
  +When you first access Kibana, you will need to specify a default index; the suggested default should work.
  +For more information on using Kibana, visit its link:https://www.elastic.co/guide/en/kibana/current/index.html[user guide].
  +
   endif::[]
  
positive.code: . link:#creating-logging-pods[Creating logging pods]
  . link:#creating-the-kibana-service[Creating the *Kibana* service]
  
  [[creating-an-elasticsearch-cluster]]
  
  === Creating an Elasticsearch cluster
  
negative.code: controller], so you can link:../dev_guide/deployments.html#scaling[scale] the
  *Elasticsearch* cluster up and down as required.
  
  You'll need a privileged service account to launch the current ElasticSearch image,
  as it runs as root (which should be corrected in time). Create a file with these contents:
  
  
  ====
  
  [source,yaml]
  ----
  apiVersion: v1
  kind: ServiceAccount
  metadata:
    name: es-deploy
  ----
  
  ====
  
  Save this to a file and create it:
  
  ====
  ----
  $ oc create -f path/to/serviceaccount.yaml
  ----
  ====
  
  You should then add this service account to the user list in the privileged
  SCC. Of course, this must be done using cluster-administrator credentials.
  
  ====
  ----
  $ oc edit scc/privileged
  ----
  ====
  
  Add this to the `users` hash at the end (`default` is the project name):
  
  ----
  - system:serviceaccount:default:es-deploy
  ----
  
  Then save and exit. This account now has access to deploy privileged pods.
  
  The following is the manifest for the *ElasticSearch* cluster:
  
  ====
  
  