anchor.diff:  
   Consider the following when deploying service mesh:
   
  -* It does not have feature parity with the existing routing plane in <% vars.product_short %>. 
  +* It does not have feature parity with the existing routing plane in <%= vars.product_short %>. 
   * It is for deployments with fewer than 20,000 routes. At greater scale, it may impact core platform functions. 
   * The control plane is not HA and registration of new routes may be delayed during upgrade. 
positive.code: <tr>
  	<td>istio-control</td>
  	<td>copilot, pilot-discovery</td>
  	<td>Propagates <% vars.product_short %> external routes to all service mesh routers.</td>
  </tr>
  <tr>
  	<td>route-syncer</td>
  
negative.code: owner: CF Networking Service Mesh
  ---
  
  This topic describes service mesh for <%= vars.product_full %>. 
  
  ## <a id="overview"></a> Overview 
  
  <%= vars.product_short %> includes an optional, beta routing plane that uses a service mesh. A service mesh provides traffic management, security and observability for microservices. For more information, see [What is a service mesh?](https://istio.io/docs/concepts/what-is-istio/#what-is-a-service-mesh) in the Istio documentation. Service Mesh in 
  
  <%= vars.product_short %> uses [Istio Pilot](https://istio.io/docs/concepts/what-is-istio/#pilot) and [Envoy](https://www.envoyproxy.io/). The Cloud Foundry [istio-release](https://github.com/cloudfoundry/istio-release) packages these components into a BOSH release. 
  
  ## <a id="components"></a> Component VMs
  
  