<p>Having AWS EKS cluster in VPC with CIDR 172.20.0.0/16 and installed <code>istio 1.0.2</code> with helm:</p>

<pre><code>helm upgrade -i istio install/kubernetes/helm/istio \
--namespace istio-system \
--set tracing.enabled=true \
--set grafana.enabled=true \
--set telemetry-gateway.grafanaEnabled=true \
--set telemetry-gateway.prometheusEnabled=true \
--set global.proxy.includeIPRanges="172.20.0.0/16" \
--set servicegraph.enabled=true \
--set galley.enabled=false
</code></pre>

<p>Then deploy some pods for testing:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
  name: service-one
  labels:
    app: service-one
spec:
  ports:
  - port: 80
    targetPort: 8080
    name: http
  selector:
    app: service-one
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: service-one
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: service-one
    spec:
      containers:
      - name: app
        image: gcr.io/google_containers/echoserver:1.4
        ports:
        - containerPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: service-two
  labels:
    app: service-two
spec:
  ports:
  - port: 80
    targetPort: 8080
    name: http-status
  selector:
    app: service-two
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: service-two
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: service-two
    spec:
      containers:
      - name: app
        image: gcr.io/google_containers/echoserver:1.4
        ports:
        - containerPort: 8080
</code></pre>

<p>and deploy it with:</p>

<pre><code>kubectl apply -f &lt;(istioctl kube-inject -f app.yaml) 
</code></pre>

<p>Then inside service-one pod, I'm requesting service-two and there are no logs about outgoing request inside service-one's istio-proxy container, but if I reconfigure istio without setting <code>global.proxy.includeIPRanges</code> it works as expected (but I need this config to allow multiple external connections). How can I debug what is going on?</p>

andfadeev
<p>Setting <code>global.proxy.includeIPRanges</code> is deprecated and should not work. There was a <a href="https://github.com/istio/istio/issues/6146" rel="nofollow noreferrer">discussion</a> on Git about this. The new closest thing is <code>includeOutboundIpRanges</code> in pod's sidecar-injector Config-Map or <code>traffic.sidecar.istio.io/includeOutboundIPRanges</code> pod annotation. Annotation looks easier. For now, it is not clear in the official documentation.</p>

<p>You could add the annotation to your deployment:</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  annotations:
     traffic.sidecar.istio.io/includeOutboundIPRanges: "172.20.0.0/16"       
  name: service-one
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: service-one
    spec:
      containers:
      - name: app
        image: gcr.io/google_containers/echoserver:1.4
        ports:
        - containerPort: 8080
</code></pre>

<p>And the same for second deployment.</p>
