anchor.diff:  ====
   If your {product-title} installation was originally performed on a version
   previous to v1.0.8, even if it has since been updated to a newer version, follow
  -the instructions for node certificates outlined in Updating
  -Master and Node Certificates. If the node certificate does not contain the IP
  +the instructions for node certificates outlined in xref:upgrading/manual_upgrades.adoc#manual-updating-master-and-node-certificates[Updating
  +Master and Node Certificates]. If the node certificate does not contain the IP
   address of the node, then Heapster will fail to retrieve any metrics.
   ====
   endif::[]
  
positive.code: ----
  ====
  
  [WARNING]
  ====
  Setting the value using secrets will replace the internally used certificates.
  Therefore, these certificates must be valid for both the externally used host
  names as well as the external host name. For `hawkular-metrics`, this means the
  certificate must have a value of the literal string `hawkular-metrics` as well
  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:metrics-reencrypting-route[re-encrypting route] method.
  ====
  
  The following table contains more advanced configuration options, detailing all
  the secrets which can be used by the deployer:
  
negative.code: When accessing Hawkular Metrics via the API, you will only be able to perform
  reads. Writing metrics has been disabled by default. If you want for individual
  users to also be able to write metrics, you will need to set the
  `*USER_WRITE_ACCESS*`
  xref:../install_config/cluster_metrics.adoc#deployer-template-parameters[deployer template parameter]
  to *true*.
  
  However, it is recommended to use the default configuration and only have
  metrics enter the system via Heapster. If write access is enabled, any user
  