anchor.diff:  |If set to *true*, the deployer will try to delete all the existing components before trying to redeploy.
   
   |`*HAWKULAR_METRICS_HOSTNAME*`
  -|External host name where clients can reach Hawkular Metrics.
  +|External host name where clients can reach Hawkular Metrics.  This is the FQDN of the machine running the router pod.
   
   |`*MASTER_URL*`
   |Internal URL for the master, for authentication retrieval.
  
positive.code: your metrics will be stored to a
  xref:../architecture/additional_concepts/storage.adoc#persistent-volumes[persistent
  volume] and be able to survive a pod being restarted or recreated. This is
  ideal if you require your metrics data to be guarded from data loss.
  
  The size of the persisted volume can be specified with the `CASSANDRA_PV_SIZE`
  xref:../install_config/cluster_metrics.adoc#deployer-template-parameters[template
  
negative.code: volume claims] is handled by the
  xref:../install_config/cluster_metrics.adoc#metrics-deployer[Metrics Deployer].
  
  {product-title} metrics also supports
  link:https://github.com/openshift/origin-metrics/blob/master/metrics.yaml#L130[dynamically
  provisioned persistent volumes]. To use this feature with {product-title}
  metrics, it is necessary to add an additional flag to the metrics-deployer:
  `DYNAMICALLY_PROVISION_STORAGE=true`.
  
  At this time, EBS, GCE, and Cinder storage back-ends can be used to
  xref:../install_config/persistent_storage/dynamically_provisioning_pvs.adoc#install-config-persistent-storage-dynamically-provisioning-pvs[dynamically
  provision persistent volumes].
  
  [[metrics-non-persistent-storage]]
  === Non-Persistent Storage
  