<commit_before>---
title: Service Mesh (Beta)
owner: CF Networking Service Mesh
---

This topic describes service mesh for <%= vars.product_full %>. 

<% if vars.product_name == "CF" %>
To deploy service mesh, see [Deploying Service Mesh (Beta)](../running/deploying-service-mesh.html). 
<% else %>
To deploy service mesh, see [Deploying Service Mesh (Beta)](../opsguide/deploying-service-mesh.html).
<% end %>

## <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 and Envoy. The Cloud Foundry `istio-release` packages these components into a BOSH release. For more information, see the following:

* The [Pilot](https://istio.io/docs/concepts/what-is-istio/#pilot) section in Istio documentation. 
* The [What is Envoy](https://www.envoyproxy.io/docs/envoy/latest/intro/what_is_envoy) topic in the Envoy documentation. 
* The [istio-release](https://github.com/cloudfoundry/istio-release) repository in GitHub. 

Service mesh deploys an additional router and runs as a parallel routing plane as illustrated in the following diagram:

![A load balancer receives requests at *.YOUR-APPS-DOMAIN and forwards them to the Gorouter. The Gorouter then forwards them to an app. A separate load balancer receives requests at *.mesh.YOUR-APPS-DOMAIN and forwards them to the istio-router. The istio-router then forwards them to an app](service-mesh.png)

## <a id="features"></a> Features

Service mesh currently supports configuring routing weights for app. For more information, see [Using Weighted Routing (Beta)](../devguide/weighted-routing.html).

## <a id="limitations"></a> Limitations

Consider the following when deploying service mesh:

* 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. 

## <a id="components"></a> Component VMs<commit_msg>adds note about domain not being configurable<commit_after>---
title: Service Mesh (Beta)
owner: CF Networking Service Mesh
---

This topic describes service mesh for <%= vars.product_full %>. 

<% if vars.product_name == "CF" %>
To deploy service mesh, see [Deploying Service Mesh (Beta)](../running/deploying-service-mesh.html). 
<% else %>
To deploy service mesh, see [Deploying Service Mesh (Beta)](../opsguide/deploying-service-mesh.html).
<% end %>

## <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 and Envoy. The Cloud Foundry `istio-release` packages these components into a BOSH release. For more information, see the following:

* The [Pilot](https://istio.io/docs/concepts/what-is-istio/#pilot) section in Istio documentation. 
* The [What is Envoy](https://www.envoyproxy.io/docs/envoy/latest/intro/what_is_envoy) topic in the Envoy documentation. 
* The [istio-release](https://github.com/cloudfoundry/istio-release) repository in GitHub. 

Service mesh deploys an additional router and runs as a parallel routing plane as illustrated in the following diagram:

![A load balancer receives requests at *.YOUR-APPS-DOMAIN and forwards them to the Gorouter. The Gorouter then forwards them to an app. A separate load balancer receives requests at *.mesh.YOUR-APPS-DOMAIN and forwards them to the istio-router. The istio-router then forwards them to an app](service-mesh.png)

## <a id="features"></a> Features

Service mesh currently supports configuring routing weights for app. For more information, see [Using Weighted Routing (Beta)](../devguide/weighted-routing.html).

## <a id="limitations"></a> Limitations

Consider the following when deploying service mesh:

* 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. 
* The domain for routes is `*.mesh.YOUR-APPS-DOMAIN` and is not configurable. 

## <a id="components"></a> Component VMs
{'fraction_non_alphanumeric': 0.10603253036854025, 'fraction_numerical': 0.0020588840848260242, 'mean_word_length': 4.596774193548387, 'pattern_counts': {'":': 0, '<': 33, '<?xml version=': 0, '>': 33, 'https://': 8, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '205764', 'n_tokens_mistral': 1453, 'n_tokens_neox': 1343, 'n_words': 551}