Cf istio config fix (#258)

* Update requirements.md

Updated Istio configuration: Virtual Service and WorkflowTemplate configurations

* Update requirements.md

Added WorkflowTemplate configuration for Istio

* Update istio configuration

Added virtual service example for runtime 0.0. 543 and higher

* Update requirements.md

* Update requirements.md

Added note on webhook - to be clarified with Yarik

Author: NimRegev

_docs/runtime/requirements.md

@@ -216,13 +216,58 @@ Configure the ingress controller to handle TCP requests.
 #### Cluster routing service
 >  The cluster routing service must be configured _after_ installing the hybrid runtime.
 
-Configure the `VirtualService` to route traffic to the `app-proxy` and `webhook` services, as in the examples below.  
+Based on the runtime version, you need to configure a single or different `VirtualService` resources for these services:
+
+##### Runtime version 0.0.543 or higher
+Configure a single `VirtualService` resource to route traffic to the `app-proxy`, `webhook`, and `workflow` services, as in the example below.  
+
+```yaml
+apiVersion: networking.istio.io/v1alpha3
+kind: VirtualService
+metadata:
+  namespace: pov-codefresh-istio-runtime # replace with your runtime name
+  name: internal-router
+spec:
+  hosts:
+    -  pov-codefresh-istio-runtime.sales-dev.codefresh.io   # replace with your host name
+  gateways:
+    - istio-system/internal-router  # replace with your gateway name
+  http:
+    - match:
+      - uri:
+          prefix: /webhooks
+      route:
+      - destination:
+          host: internal-router
+          port:
+            number: 80
+    - match:
+      - uri:
+          prefix: /app-proxy
+      route:
+      - destination:
+          host: internal-router
+          port:
+            number: 80
+    - match:
+      - uri:
+          prefix: /workflows
+      route:
+      - destination:
+          host: internal-router
+          port:
+            number: 80
+```
+
+##### Runtime version 0.0.542 or lower
+
+Configure two different `VirtualService` resources, one to route traffic to the `app-proxy`, and the second to route traffic to the `webhook` services, as in the examples below.  
 
 {::nomarkdown}
 </br>
 {:/}
 
-**`VirtualService` example for `app-proxy`:** 
+**`VirtualService` example for `app-proxy`:**
 
 ```yaml
 apiVersion: networking.istio.io/v1alpha3
@@ -234,7 +279,7 @@ spec:
   hosts:
     - my.support.cf-cd.com # replace with your host name
   gateways:
-    - my-gateway
+    - my-gateway # replace with your host name
   http:
     - match:
       - uri:
@@ -249,7 +294,9 @@ spec:
 </br>
 {:/}
 
-**`VirtualService` example for `webhook`:** 
+**`VirtualService` example for `webhook`:**  
+
+> Configure a `webhook` for each event defined in the event source.
 
 ```yaml  
 apiVersion: networking.istio.io/v1alpha3
@@ -261,7 +308,7 @@ spec:
   hosts:
     - my.support.cf-cd.com # replace with your host name
   gateways:
-    - my-gateway
+    - my-gateway # replace with your gateway name
   http:
     - match:
       - uri:
@@ -272,6 +319,9 @@ spec:
           port:
             number: 80
 ```
+
+
+
 {::nomarkdown}
 </br></br>
 {:/}