anchor.diff:  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
  
positive.code: [[metrics-using-secrets-byo-certs]]
  ==== Providing Your Own Certificates
  
  To provide your own certificates and replace the internally used ones, you
  can pass these values as xref:../dev_guide/secrets.adoc#dev-guide-secrets[secrets] to the
  Metrics Deployer.
  
  [NOTE]
  ====
  Alternatively, you can use a
  xref:../install_config/cluster_metrics.adoc#metrics-reencrypting-route[re-encrypting
  route] which allow the self-signed certificates to remain in use internally
  while allowing your own certificates to be used for externally access. To use a
  re-encrypting route, do not set the certificates as a secret, but a secret named
  *metrics-deployer* must still exist before the Metrics Deployer can complete.
  
negative.code: 
  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].
  
  [[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
  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
  