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
Now we have multiple replicas of Torchserve running and istio installed. We can apply gateway, virtual service and destination rule to enable session affinity to the user requests.
306
+
307
+
- Apply the istio gateway via `kubectl apply -f gateway.yaml`
308
+
- This gateway exposes all the host behind it via port 80 as defined in the yaml file.
309
+
- Apply the virtual service with command `kubectl apply -f virtual_service.yaml`
310
+
- This with look for header named `protocol` in the incoming request and forward the request to Torchserve service. If the `protocol` header has a value `rest` then the request is forwarded to port `8080` of Torchserve service and if the `protocol` header has a value `grpc` then the request is forwarded to port `7070` for Torchserve service.
311
+
- Apply the destination Rule using the command `kubectl apply -f destination_rule.yaml`.
312
+
- The destination rule look for a http cookie with a key `session_id`. The request with `session_id` is served by the same pod that served the previous request with the same `session_id`
313
+
314
+
### HTTP Inference
315
+
316
+
- Fetch the external IP from istio-ingress gateway using the below command
0 commit comments