anchor.diff:  ifdef::openshift-enterprise[]
   [NOTE]
   ====
  -With Aggregated Logging version 3.2.1, Curator is available for use as Tech Preview.
  -To start it, after completing an installation using the 3.2.1 Deployer, scale up
  -the Curator deployment config that was created (defaults to zero replicas).
  -
  -There should be one Curator pod running per Elasticsearch cluster.  If you deployed
  -Aggregated Logging with `ENABLE_OPS_CLUSTER=true` then you will have a second
  -deployment config, one for the ops cluster and one for the non-ops cluster.
  +With Aggregated Logging version 3.2.1, Curator is available for use as Tech
  +Preview. To start it, after completing an installation using the 3.2.1 Deployer,
  +scale up the Curator deployment configuration that was created. (It defaults to
  +zero replicas.)
  +
  +There should be one Curator pod running per Elasticsearch cluster. If you
  +deployed aggregated logging with `ENABLE_OPS_CLUSTER=true`, then you will have a
  +second deployment configuration (one for the ops cluster and one for the non-ops
  +cluster).
   
   ----
   $ oc scale dc/logging-curator --replicas=1
  
positive.code: 
  You can also specify default values for the run hour, run minute, and age in days
  of the indices when processing the Curator template. Use `CURATOR_RUN_HOUR` and
  `CURATOR_RUN_MINUTE` to set the default runhour and runminute, and use
  `CURATOR_DEFAULT_DAYS` to set the default index age.
  
negative.code: ====
  endif::openshift-enterprise[]
  
  Curator allows administrators to configure scheduled Elasticsearch maintenance
  operations to be performed automatically on a per-project basis. It is scheduled
  to perform actions daily based on its configuration. Only one Curator pod is
  recommended per Elasticsearch cluster. Curator is configured via a mounted YAML
  configuration file with the following structure:
  
  ====
  ----
  