K
Q

same prefix http request mis-forward by istio VirtualService

11/11/2019

the log of istio-ingressgateway:

[2019-11-11T06:09:02.823Z] "GET /notebook/name/test-root1/ HTTP/2" 404 -... outbound|80||test-root.name.svc.cluster.local - ...-

my http request with uri :/notebook/name/test-root1/ was forward to host test-root.name.svc.cluster.local , while there are two VirtualService's named "test-root" and "test-root1",respectively. Thus lead to a 404 error for test-root1.

Any ideas about how to fix it? Thanks a lot,XD.

-- fresh learning
istio
kubernetes

Similar Questions

How to add HAproxy on Kafka broker
kubernetes Client-go kubectl rollout example
Add custom response on 413 status code using the Nginx Ingress Controller
Share s3fs volume in Kubernetes with two containers in a pod with same subpath
Docker container with my java-app fails with standard_init_linux.go:190: exec user process caused "exec format error"
Kubernetes - resolve hostname of a service

1 Answer

11/12/2019

i figure out how this problem came out yesterday, the Kubeflow notebook-controller use istio proxy and set the match scheme as: prefix. But they carelessly set the match uri as xxx/xxx which lead to request like xxx/xxxabc mis-forward.

And they have fixed this bug few days ago, as the pr mentioned in the comment.

-- fresh learning
Source: StackOverflow