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: secret].
  ====
  
  By default, the Hawkular Metrics server uses self-signed certificates, which are
  not trusted by a browser or other external services. If you want to provide your
  own trusted certificate to be used for external access, you can do so using a
  route with a
  link:../architecture/core_concepts/routes.html#secured-routes[re-encryption
  termination] after deploying the metrics components.
  
  . First, delete the default route that uses the self-signed certificates:
  +
  
negative.code: $ oc delete route hawkular-metrics
  ----
  
  . A new route with link:../architecture/core_concepts/routes.html#secured-routes[re-encryption termination]
  will then need to be created.
  +
  ====
  ----
  $ oc create route reencrypt hawkular-metrics-reencrypt \
              --hostname hawkular-metrics.example.com \ <1>
              --key /path/to/key \ <2>
              --cert /path/to/cert \ <2>
              --ca-cert /path/to/ca.crt \ <2>
  ifdef::openshift-enterprise[]
              --service hawkular-metrics --port 8444 \
  endif::[]
  ifdef::openshift-origin[]
              --service hawkular-metrics --port 8443 \
  endif::[]
              --dest-ca-cert /path/to/internal-ca.crt <3>
  ----
  <1> The value specified in the *HAWKULAR_METRICS_HOSTNAME* template parameter.
  <2> These need to define the custom certificate you wish to provide.
  