anchor.diff:  
   Consider the following when deploying service mesh:
   
  -* It does not have feature parity with the existing routing plane in CF. 
  -* It currently only supports ingress routing to apps. 
  -* It is for deployments with fewer than 20,000 routes. At greater scale, it impacts core platform functions. 
  -
  -## <a id="deploy"></a> How to Deploy
  -
  -To deploy service mesh, see...+* 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. 
positive.code: </tr>
  <tr>
  	<td>istio-router</td>
  	<td></td>
  	<td></td>
  </tr>
  <tr>
  	<td>istio-control</td>
  	<td></td>
  	<td></td>
  </tr>
  <tr>
  	<td>cc-route-syncer</td>
  	<td></td>
  	<td></td>
  </tr>
  </table>
  
  To see the communication ports and protocols used by these components, see...
  
  ## <a id="features"></a> Features
  
  
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
  
  Service mesh deploys an additional router and runs as a parallel routing plane as illustrated in the following diagram:
  
  ![Istio plane](istio-plane.png)
  
  The following table describes each VM deployed as part of service mesh in <% vars.product_short %>, along with their function.
  
  <table>
  <tr>
  