anchor.diff:  |Variables for the operations log cluster.
   |===
   +
  +[NOTE]
  +====
   When setting the `*ENABLE_OPS_CLUSTER*` parameter to `*true*`, Fluentd splits
   logs between the Elasticsearch cluster and a cluster reserved for operations
   logs. This means a second Elasticsearch and Kibana are deployed. The deployments
   are distinguishable by the *-ops* included in their names.
  -+
  -This creates a deployer pod and prints its name. Wait until the pod
  -is running; this can take up to a few minutes to retrieve the deployer
  -image from its registry. You can watch it with:
  -+
  -    $ oc get pod/<pod_name> -w
  -+
  -If it seems to be taking too long, you can retrieve more details about the pod and
  -any associated events with:
  -+
  -    $ oc describe pod/<pod_name>
  -+
  -When it runs, check the logs of the resulting pod (`oc logs -f <pod_name>`)
  -for some instructions to follow after deployment. More details
  -are given below.
  -
  -. As a cluster administrator, deploy a template that is created by
  -the deployer:
  +====
  ++
  +Running the deployer creates a deployer pod and prints its name. Wait until the
  +pod is running. This can take up to a few minutes to retrieve the deployer image
  +from the registry. You can watch its process with:
  ++
  +----
  +$ oc get pod/<pod_name> -w
  +----
  ++
  +If it seems to be taking too long, you can retrieve more details about the pod
  +and any associated events with:
  ++
  +----
  +$ oc describe pod/<pod_name>
  +----
  ++
  +When it runs, you can check the logs of the resulting pod to see if the
  +deployment was successful:
  ++
  +----
  +$ oc logs -f <pod_name>
  +----
  +
  +. As a cluster administrator, deploy a template that is created by the deployer:
   +
   ====
   ----
  
positive.code: . Create a link:../dev_guide/secrets.html[secret] for the deployer. The secret
  can be configured specifically for your instance of the deployer.
  +
  A set of files can be supplied in the secret:
  +
  [cols="2",options="header"]
  |===
  
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
  