anchor.diff:  
   The Metrics Deployer deploys and configures all of the metrics components. You
   can configure it by passing in information from
  -xref:../dev_guide/secrets.adoc#dev-guide-secrets[secrets] and by passing parameters to the Metrics
  -Deployer's xref:../architecture/core_concepts/templates.adoc#architecture-core-concepts-templates[template].
  +xref:../dev_guide/secrets.adoc#dev-guide-secrets[secrets] and by passing
  +parameters to the Metrics Deployer's
  +xref:../architecture/core_concepts/templates.adoc#architecture-core-concepts-templates[template].
   
   [[metrics-deployer-using-secrets]]
   === Using Secrets
   
   By default, the Metrics Deployer auto-generates self-signed certificates for use
   between components. Because these are self-signed certificates, they are not
  -automatically trusted by a web browser. Therefore, it is recommended to use your
  -own certificates for anything being accessed outside of the {product-title}
  -cluster. This is especially important for the Hawkular Metrics server as it must
  -be accessible in a browser for the web console to function.
  +automatically trusted by a web browser. Therefore, it is recommended to use
  +internal certificates for anything being accessed outside of the {product-title}
  +cluster, and then use the re-encrypting route to provide your own custom
  +certificates. This is especially important for the Hawkular Metrics server as it
  +must be accessible in a browser for the web console to function.
   
   The Metrics Deployer requires that you manually create a *metrics-deployer*
   secret whether you are xref:metrics-using-secrets-byo-certs[providing your own
  
positive.code: as the value specified in `*HAWKULAR_METRICS_HOSTNAME*`.
  
  If you are unable to add the internal host name to your certificate, then you
  can use the
  xref:../install_config/cluster_metrics.adoc#metrics-reencrypting-route[re-encrypting
  route] method.
  ====
  
  The following table contains more advanced configuration options, detailing all
  
negative.code: properly.
  
  |===
  
  The Heapster component uses the service name DNS registry to connect to Hawkular
  Metrics. In the metrics code, the URL used by Heapster to connect to Hawkular
  Metrics is hard-coded. It attaches the search domain and resolves to the service
  IP.
  
  [[metrics-using-secrets-autogenerated]]
  ==== Using Generated Self-Signed Certificates
  