In the guide https://istio.io/docs/tasks/traffic-management/egress.html, there is a way to access non-http traffic by includingIPRanges. However, when I follow the instructions I still am unable to access anything. Should this rule allow me to bypass istio for egress as I think it should or am I missing something?
I run a version of this command
kubectl apply -f <(istioctl kube-inject -f samples/sleep/sleep.yaml --includeIPRanges=172.30.0.0/16,172.20.0.0/16,10.10.10.0/24) is the command it suggests for bluemix users, but this does not work for me. When I try to store from my app in cloud object store I get a 500 error, however with no istio sidecar the store function works perfectly.
It works fine for me using Istio 0.2.10 on a Bluemix free tier cluster. Are you saying that the egress task doesn't even work for you, i.e., you can't do the curl suggested in the task? kubectl exec -it $SOURCE_POD -c sleep curl http://httpbin.org/headers A 500 error doesn't sound like a problem related to reach-ability anyway. That sounds like the server you're calling is crashing?