anchor.diff:  Alternatively, you can use a
   link:../install_config/cluster_metrics.html#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. If you
  -want to use a re-encrypting route, you must not set the certificates as a
  -secret, but a secret named *metrics-deployer* must still exist before the
  -Metrics Deployer can complete.
  +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.
   ====
   
   Optionally, provide your own certificate that is configured to be trusted by
  
positive.code: .Deploying without Persistent Storage
  ====
  The following command sets the Hawkular Metrics route to use
  `hawkular-metrics.example.com` and deploy without persistent storage.
  Remember, because this is being deployed without persistent storage, metric data loss
  can occur.
  
  ----
  $ oc new-app -f metrics-deployer.yaml \
  
negative.code: secret].
  ====
  
  By default, the Hawkular Metrics server uses an internally signed certificate,
  which is not trusted by browsers or other external services. To provide your own
  trusted certificate to be used for external access, use a route with
  link:../architecture/core_concepts/routes.html#secured-routes[re-encryption
  termination].
  
  Creating this new route requires deleting the default route that just passes
  through to an internally signed certificate:
  
  . First, delete the default route that uses the self-signed certificates:
  +
  