anchor.diff:  go-app   started           1/1       32M      32M  go-app.istio.example.com
   dora     started           1/1       1G       1G   go-app.istio.example.com
   </pre>
  -Running `curl  go-app.istio.example.com` results in 50% of the requests going to `go-app` and 50% of the requests going to `dora`.+If `go-app` has a weight of 9 and `dora` has a weight of 1, then running `curl  go-app.istio.example.com` results in observing 90% of the requests go to `go-app` and 10% to `dora`.
positive.code: 
  <p class="note"><strong>Note</strong>: This feature does not yet have cf CLI integration. The steps for updating a routing weight require you to curl the Cloud Controller v3 API.</p>
  
  This section describes how to configure routing weights. Repeat the steps below for each app that you want to map to the same route. 
  
  
  1. Map a route to your app using the shared domain created for Istio:
  
  	```
  	cf map-route APP-NAME SHARED-ISTIO-DOMAIN -n HOSTNAME
  	```
  	Where:
  	* `APP-NAME` is the name of the app
  	* `SHARED-ISTIO-DOMAIN` is the shared Istio domain configured by your operator. 
  	* `HOSTNAME` is the hostname to use for creating the route. The format of the route is `HOSTNAME.SHARED-ISTIO-DOMAIN`. 
  
  	For example:
  	<pre class="terminal">
  	$ cf map-route app1 istio.apps-domain.com -n app1
  	</pre>
  
  1. Get the GUID of the app:
  
  
negative.code: 1. Get the GUID of the route:
  	
  	```
  	cf curl /v2/routes?q=host:HOSTNAME
  	``` 
  	Where `HOSTNAME` is the hostname you specified when creating the route. This is generally the same as the app name.<br> 
  	The GUID of the route is located after `"metadata": {"guid":`. 
  
  1. List the route mappings associated with the route:
  