Egress Virtual Service routing matches #46238
Unanswered
CerqueiraYYZ
asked this question in
Q&A
Replies: 1 comment
-
I moved the rule f the - gateway inside the node, warnings are gone but now I just have this error message "upstream connect error or disconnect/reset before headers. reset reason: connection termination" if I add subset: mock works but timeouts are not applied. That's the way I'm using to know if is matching the route '
'
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello
I need help understanding how to match different routes in my Virtual Service, in this case, my idea is to have a route with 1 or more uri paths but the destination will be the same the only change is going to be the timeout, I want to have diff timeouts and subsets with diff CircuitBreaker rules applied.
This is my Virtual Service so far if I start to play with the timeouts doesn't work, if I add in this case the gateway - mesh I start to see conflicts on my config when I apply to them.
there is an example or a guide for this specific scenario?
`apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: direct-mock-dev-through-egress-gateway
namespace: istio-system
spec:
hosts:
gateways:
http:
headers:
request:
set:
User-Agent: egress
match:
regex: "^/passenger.*"
route:
host: mock-egressgateway.istio-system.svc.cluster.local
port:
number: 443
weight: 100
timeout: 50ms
match:
regex: "^/specialassistance"
route:
host: mock-egressgateway.istio-system.svc.cluster.local
port:
number: 443
weight: 100
timeout: 50ms
match:
port: 80
route:
host: mock-egressgateway.istio-system.svc.cluster.local
subset: mock
port:
number: 443
weight: 100
timeout: 2.5s
headers:
request:
set:
User-Agent: egress
match:
port: 443
route:
host: placeholder-host.com
port:
number: 443
weight: 100
`
Beta Was this translation helpful? Give feedback.
All reactions