You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
* Update requirements.mdUpdated Istio configuration: Virtual Service and WorkflowTemplate configurations* Update requirements.mdAdded WorkflowTemplate configuration for Istio* Update istio configurationAdded virtual service example for runtime 0.0. 543 and higher* Update requirements.md* Update requirements.mdAdded note on webhook - to be clarified with Yarik
Copy file name to clipboardExpand all lines: _docs/runtime/requirements.md
+55-5Lines changed: 55 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -216,13 +216,58 @@ Configure the ingress controller to handle TCP requests.
216
216
#### Cluster routing service
217
217
> The cluster routing service must be configured _after_ installing the hybrid runtime.
218
218
219
-
Configure the `VirtualService` to route traffic to the `app-proxy` and `webhook` services, as in the examples below.
219
+
Based on the runtime version, you need to configure a single or different `VirtualService` resources for these services:
220
+
221
+
##### Runtime version 0.0.543 or higher
222
+
Configure a single `VirtualService` resource to route traffic to the `app-proxy`, `webhook`, and `workflow` services, as in the example below.
223
+
224
+
```yaml
225
+
apiVersion: networking.istio.io/v1alpha3
226
+
kind: VirtualService
227
+
metadata:
228
+
namespace: pov-codefresh-istio-runtime # replace with your runtime name
229
+
name: internal-router
230
+
spec:
231
+
hosts:
232
+
- pov-codefresh-istio-runtime.sales-dev.codefresh.io # replace with your host name
233
+
gateways:
234
+
- istio-system/internal-router # replace with your gateway name
235
+
http:
236
+
- match:
237
+
- uri:
238
+
prefix: /webhooks
239
+
route:
240
+
- destination:
241
+
host: internal-router
242
+
port:
243
+
number: 80
244
+
- match:
245
+
- uri:
246
+
prefix: /app-proxy
247
+
route:
248
+
- destination:
249
+
host: internal-router
250
+
port:
251
+
number: 80
252
+
- match:
253
+
- uri:
254
+
prefix: /workflows
255
+
route:
256
+
- destination:
257
+
host: internal-router
258
+
port:
259
+
number: 80
260
+
```
261
+
262
+
##### Runtime version 0.0.542 or lower
263
+
264
+
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.
220
265
221
266
{::nomarkdown}
222
267
</br>
223
268
{:/}
224
269
225
-
**`VirtualService` example for `app-proxy`:**
270
+
**`VirtualService` example for `app-proxy`:**
226
271
227
272
```yaml
228
273
apiVersion: networking.istio.io/v1alpha3
@@ -234,7 +279,7 @@ spec:
234
279
hosts:
235
280
- my.support.cf-cd.com # replace with your host name
236
281
gateways:
237
-
- my-gateway
282
+
- my-gateway # replace with your host name
238
283
http:
239
284
- match:
240
285
- uri:
@@ -249,7 +294,9 @@ spec:
249
294
</br>
250
295
{:/}
251
296
252
-
**`VirtualService` example for `webhook`:**
297
+
**`VirtualService` example for `webhook`:**
298
+
299
+
> Configure a `webhook` for each event defined in the event source.
253
300
254
301
```yaml
255
302
apiVersion: networking.istio.io/v1alpha3
@@ -261,7 +308,7 @@ spec:
261
308
hosts:
262
309
- my.support.cf-cd.com # replace with your host name