Closed oleg-filiutsich closed 6 years ago
--set global.proxy.includeIPRanges="0.0.0.0/0"
I don't know why put this value but this is your issue. Put your service range instead, or create ServiceEntry rules https://istio.io/docs/tasks/traffic-management/egress/
@AWKIF Big thank you for answer. Sorry I not understood how correctly set allow IP range like 0.0.0.0/0 for access to external services. Can you give me some example?
In k8s your services are deployed on a certain ip ranges (--cluster-cidr on my kubeproxy),
Just put this network range here:
ie:
--set global.proxy.includeIPRanges="100.32.0.0/16"
From the doc:
The simplest way to use the global.proxy.includeIPRanges variable is to pass it the IP range(s) used for internal cluster services, thereby excluding external IPs from being redirected to the sidecar proxy. The values used for internal IP range(s), however, depends on where your cluster is running. For example, with Minikube the range is 10.0.0.1/24,
@AWKIF Thank you.
# For flanel net
$ helm template ~/istio-0.8.0/install/kubernetes/helm/istio --name istio --namespace istio-system --set servicegraph.enable=true --set tracing.enabled=true --set grafana.enabled=true --set servicegraph.enabled=true --set global.proxy.includeIPRanges="10.244.0.0/16" -x templates/sidecar-injector-configmap.yaml | kubectl apply -f -
at last it is works!
glad to know :) cheers !
What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details
Is Istio Auth enabled or not ? I installed istio via commands
What happened: I run my microservice. The service try use external consul server 192.168.100.15 (without kubernetes cluster) but connect blocked by istio.
What you expected to happen: Istio allow any connect to external world via IP or dns names.