anchor.diff:  == Deploying the EFK Stack
   
   The EFK stack is deployed link:../dev_guide/templates.html[using a template].
  -Ansible-based installs should create the *_logging-deployer-template_* template in the *_openshift_* project.
  -ifdef::openshift-enterprise[]
  -Otherwise, the template can be created with the following command:
  -
  -----
  -$ oc create -n openshift -f /usr/share/openshift/examples/infrastructure-templates/enterprise/logging-deployer.yaml
  -----
  -endif::openshift-enterprise[]
  -ifdef::openshift-origin[]
  -Otherwise, the template can be created with the following command:
  -
  -----
  -$ oc create -n openshift -f https://raw.githubusercontent.com/openshift/origin-aggregated-logging/master/deployment/README.md
  -----
  -endif::openshift-origin[]
   
   . Run the deployer, specifying at least the parameters in the following example (more are described in the table below):
   +
  
positive.code: $ oc process logging-support-template | oc create -f -
  ----
  ====
  
  == 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
  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
  
negative.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.
  