From 73bd6581764c052a52580f7ac7cf8cc91631c62f Mon Sep 17 00:00:00 2001 From: Tsuyoshi Ushio Date: Tue, 11 Jul 2017 04:54:14 +0900 Subject: [PATCH] Adding Azure IPRanges (#404) --- _docs/tasks/egress.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/_docs/tasks/egress.md b/_docs/tasks/egress.md index 8a4d163085..1e72c8e3e3 100644 --- a/_docs/tasks/egress.md +++ b/_docs/tasks/egress.md @@ -146,6 +146,13 @@ servicesIpv4Cidr: 10.7.240.0/20 kubectl apply -f <(istioctl kube-inject -f samples/apps/sleep/sleep.yaml --includeIPRanges=10.4.0.0/14,10.7.240.0/20) ``` +On Azure Container Service(ACS), use: + +```bash +kubectl apply -f <(istioctl kube-inject -f samples/apps/sleep/sleep.yaml --includeIPRanges=10.244.0.0/16,10.240.0.0/16) +``` + + After starting your service this way, the Istio sidecar will only intercept and manage internal requests within the cluster. Any external request will simply bypass the sidecar and go straight to its intended destination.