anchor.diff:  $ 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 3 for resiliency to node failures. Each instance
  +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
  
positive.code: ====
  
  You will need to scale Fluentd if nodes are added or subtracted.
  
  === Kibana
  
  
negative.code: link:../admin_guide/managing_projects.html#using-node-selectors[node
  selector] on the project is not recommended, as this would restrict
  where Fluentd can be deployed. Instead, specify node selectors for the
  deployer to be applied on your other deployment configurations.
  ====
  
  . Create a link:../dev_guide/secrets.html[secret] for the deployer. The secret
  can be configured specifically for your instance of the deployer.
  +
  