anchor.diff:  ----
   
   === Re-encryption Termination
  -Re-encryption is a special case of edge termination where the traffic is first decrypted with certificate A and then
  -re-encrypted with certificate B when sending the traffic to the destination.
  -
  -Re-encryption termination is configured by setting `TLS.Termination` to reencrypt and providing the `CertificateFile`,
  -`KeyFile`, the `CACertificateFile`, and a `DestinationCACertificateFile`. The edge certificates remain the same as in the edge
  -termination use case. The `DestinationCACertificateFile` is used in order to validate the secure connection from the router
  -to the destination (implemenation specific).
  +Re-encryption is a type of edge termination where the client encrypts communication with a certificate, which is then re-encrypted with a separate 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 providing the `CertificateFile`, `KeyFile`, the `CACertificateFile`, and a `DestinationCACertificateFile`. The edge certificates remain the same as in the edge termination use case. The `DestinationCACertificateFile` is used in order to validate the secure connection from the router to the destination (implemenation specific).
   
   ----
   {
  
positive.code: 
  == HA Routers
  
  Highly available router setups can be accomplished by running multiple instances of the router pod and fronting them
  with a balancing tier. This could be something as simple as DNS round robin or as complex as multiple load balancing layers.
  
  === DNS Round Robin
  
  As a simple example, you may create a zone file for a DNS server like BIND that maps
  multiple A records for a single domain name.  When clients do a lookup they will be given one of the many records, in order,
  as a round robin scheme.  The files below illustrate an example of using wild card DNS with multiple A records to achieve
  the desired round robin.  The wild card could be further distributed into shards with `*.<shard>`.  Finally, a test using
  `dig` (available in the `bind-utils` package) is shown from the vagrant environment that shows multiple answers for the
  same lookup.  Doing multiple pings show the resolution swapping between IP addresses.
  
  
  
  
negative.code: === Passthrough Termination
  Passthrough termination is a mechanism to send encrypted traffic straight to the destination without the router providing TLS termination.
  
  Passthrough termination is configured by setting `TLS.Termination` to passthrough on your route. No other information is required. The destination (such as an Nginx, Apache, or another HAProxy instance) will be responsible for serving certificates for the traffic.
  
  ----
  {
  