Hi, I have recently installed 1.1 and I have some issues:
Every second request fails. Not half of requests (that would indicate some randomness) but really every second one gives me
400 Bad Request with a message (in body)
app prober config does not exists for /my/path. At this point I am not doing anything fancy; Just one gateway (on port 80), one virtualservice rewriting the path and 3 subsets to match. I can see those logs also in
istio-ingressgateway. Strange enough, Kiali reports all requests being successful.
I can’t get intra-mesh communication to work (I had that problem just before reinstall, though). I have a pod with application that can call other HTTP endpoint -
/proxy?url=http://some.url:8080 and passes the result. When I
oc exec into the container I can run
curl http://app.my-namespace.svc.cluster.local:8080/foo without issues, but when I call that app even within it (through
curl localhost:8080/proxy?url=http://app.my-namespace.svc.cluster.local:8080/foo) it gives me 404. Since
curl works, the problem is probably not in the sidecar receiving the communication but in the one attached to the node which is initiating it. Strange enough, I’d expect that the iptable rules apply to myself as exec’d user as well.