anchor.diff:  ====
   
   You will need to scale Fluentd if nodes are added or subtracted.
  +endif::openshift-enterprise[]
  +
  +ifdef::openshift-origin[]
  +Once Elasticsearch is running, label nodes to enable Fluentd to run on them
  +and feed logs to Elasticsearch. Use the `*FLUENTD_NODESELECTOR*` given to
  +the deployer (if different) in the command below:
  +
  +====
  +----
  +$ oc label nodes --all logging-infra-fluentd=true
  +----
  +====
  +
  +endif::openshift-origin[]
   
   === Kibana
   
  
positive.code: ====
  
  These deployments will be named differently, but all will have the
  'logging-es' prefix. You should be aware of the cluster
  parameters (described in the deployer parameters) based on cluster size
  that may need corresponding adjustment in the template as well as
  existing deployments.
  
negative.code: $ oc process logging-support-template | oc create -f -
  ----
  ====
  endif::openshift-enterprise[]
  
  == Post-deployment Configuration
  
  === Elasticsearch
  
  In any production employment, Elasticsearch should be deployed with a
  cluster size of at least three for resiliency to node failures. Each instance
  requires individual storage, but an OpenShift deployment can only provide
  volumes shared by all its pods, so the Elasticsearch cluster cannot be
  implemented with a single deployment. The EFK deployer instead creates one
  