anchor.diff:  router
   ----
   
  +====
  +
   ==== Data Flow
   
   The following diagram illustrates how data flows from the master through the plugin and finally into a HAProxy configuration.
  
positive.code:     *       IN      A       10.245.2.2
              IN      A       10.245.2.3
  
  #### Testing the entry
  
  
      [vagrant@openshift-master ~]$ dig hello-openshift.shard1.v3.rhcloud.com
  
  
negative.code: ----
  
  === Re-encryption Termination
  Re-encryption is a type of edge termination where the client encrypts communication with a certificate, which is then re-encrypted with a different certificate when the traffic reaches the destination; with the router using health checks to determine the authenticity of the host.
  
  Re-encryption termination is configured by setting `tls:termination` to `reencrypt` and specifying the `certificate`, `key`, and `caCertificate`, as well as the `destinationCACertificate`. The edge termination certificates remain the same as in the edge termination use case. The `destinationCaCertificate` is used in order to validate the secure connection from the router to the destination, and is specific to each implemenation:
  
  ----
  {
  