anchor.diff:  $ oc delete sa/logging-deployer secret/logging-deployer
   ----
   
  -To remove everything generated without having to destroy the project:
  +Similarly, you can remove everything generated during the deployment that will
  +not destroy the project:
   
   ----
   $ oc delete all --selector logging-infra=kibana
   $ oc delete all --selector logging-infra=fluentd
   $ oc delete all --selector logging-infra=elasticsearch
   $ oc delete all,sa,oauthclient --selector logging-infra=support
  -$ oc delete secret logging-fluentd logging-elasticsearch logging-es-proxy logging-kibana logging-kibana-proxy logging-kibana-ops-proxy
  +$ oc delete secret logging-fluentd logging-elasticsearch \
  +    logging-es-proxy logging-kibana logging-kibana-proxy \
  +    logging-kibana-ops-proxy
   ----
   
   == Troubleshooting Kibana
  
positive.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
  node selector.
  
  To configure a node selector, edit each deployment configuration and add the
  `*nodeSelector*` parameter to specify the label of the desired nodes:
  
negative.code: 
  [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
  