anchor.diff:  ----
   $ base64 -d <<< \
       `oc get -o yaml secrets hawkular-metrics-certificate \
  -    | grep -i hawkular-metrics-ca.certificate | awk '{print $2}'`
  -----
  -
  -. Save your route definition to a file, for example *_metrics-reencrypt.yaml_*,
  -and create it:
  -+
  -----
  -$ oc create -f metrics-reencrypt.yaml
  -----
  +    | grep -i hawkular-metrics-ca.certificate | awk '{print $2}'` \
  +    > /path/to/internal-ca.crt
  +----
  +
   
   [[configuring-openshift-metrics]]
   == Configuring OpenShift
  
positive.code: You must have a persistent volume of sufficient size available.
  
  ----
  $ oc process -f metrics-deployer.yaml -v \
      HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com \
      | oc create -f -
  ----
  ====
  
  .Deploying without Persistent Storage
  ====
  The following command sets the Hawkular Metrics route to use
  `hawkular-metrics.example.com` and is deployed without persistent storage.
  Remember, this is being deployed without persistent storage, so metrics data loss
  can occur.
  
  ----
  $ oc process -f metrics-deployer.yaml -v \
      HAWKULAR_METRICS_HOSTNAME=hawkular-metrics.example.com,USE_PERSISTENT_STORAGE=false \
      | oc create -f -
  ----
  ====
  
  
negative.code: secret].
  ====
  
  By default the Hawkular Metrics server uses an internally-signed certificate which is not
  trusted by browsers or other external services. If you wish to provide your own trusted
  certificate to be used for external access you can do so using 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:
  +
  