• Egress Gateways
    • Use case
    • Before you begin
    • Deploy Istio egress gateway
    • Egress gateway for HTTP traffic
      • Cleanup HTTP gateway
    • Egress gateway for HTTPS traffic
      • Cleanup HTTPS gateway
    • Additional security considerations
    • Apply Kubernetes network policies
      • Cleanup network policies
    • Troubleshooting
    • Cleanup
    • See also

    Egress Gateways

    This example does not work in Minikube.

    The Control Egress Traffic task shows how to configureIstio to allow access to external HTTP and HTTPS services from applications inside the mesh.There, the external services are called directly from the client sidecar.This example also shows how to configure Istio to call external services, although this timeindirectly via a dedicated egress gateway service.

    Istio uses ingress and egress gatewaysto configure load balancers executing at the edge of a service mesh.An ingress gateway allows you to define entry points into the mesh that all incoming traffic flows through.Egress gateway is a symmetrical concept; it defines exit points from the mesh. Egress gateways allowyou to apply Istio features, for example, monitoring and route rules, to traffic exiting the mesh.

    Use case

    Consider an organization that has a strict security requirement that all traffic leavingthe service mesh must flow through a set of dedicated nodes. These nodes will run on dedicated machines,separated from the rest of the nodes running applications in the cluster. These special nodes will servefor policy enforcement on the egress traffic and will be monitored more thoroughly than other nodes.

    Another use case is a cluster where the application nodes don’t have public IPs, so the in-mesh services that runon them cannot access the Internet. Defining an egress gateway, directing all the egress traffic through it, andallocating public IPs to the egress gateway nodes allows the application nodes to access external services in acontrolled way.

    Before you begin

    • Setup Istio by following the instructions in the Installation guide.

    • Deploy the sleep sample app to use as a test source for sending requests.If you haveautomatic sidecar injectionenabled, run the following command to deploy the sample app:

    Zip

    1. $ kubectl apply -f @samples/sleep/sleep.yaml@

    Otherwise, manually inject the sidecar before deploying the sleep application with the following command:

    Zip

    1. $ kubectl apply -f <(istioctl kube-inject -f @samples/sleep/sleep.yaml@)

    You can use any pod with curl installed as a test source.

    • Set the SOURCE_POD environment variable to the name of your source pod:
    1. $ export SOURCE_POD=$(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name})
    • Enable Envoy’s access logging

    Deploy Istio egress gateway

    • Check if the Istio egress gateway is deployed:
    1. $ kubectl get pod -l istio=egressgateway -n istio-system

    If no pods are returned, deploy the Istio egress gateway by performing the next step.

    • Run the following command:
    1. $ istioctl manifest apply --set values.global.istioNamespace=istio-system \
    2.     --set values.gateways.istio-ingressgateway.enabled=false \
    3.     --set values.gateways.istio-egressgateway.enabled=true

    The following instructions create a destination rule for the egress gateway in the default namespaceand assume that the client, SOURCE_POD, is also running in the default namespace.If not, the destination rule will not be found on thedestination rule lookup pathand the client requests will fail.

    Egress gateway for HTTP traffic

    First create a ServiceEntry to allow direct traffic to an external service.

    • Define a ServiceEntry for edition.cnn.com:
    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: ServiceEntry
    4. metadata:
    5.   name: cnn
    6. spec:
    7.   hosts:
    8.   - edition.cnn.com
    9.   ports:
    10.   - number: 80
    11.     name: http-port
    12.     protocol: HTTP
    13.   - number: 443
    14.     name: https
    15.     protocol: HTTPS
    16.   resolution: DNS
    17. EOF
    • Verify that your ServiceEntry was applied correctly by sending an HTTP request to http://edition.cnn.com/politics.
    1. $ kubectl exec -it $SOURCE_POD -c sleep -- curl -sL -o /dev/null -D - http://edition.cnn.com/politics
    2. HTTP/1.1 301 Moved Permanently
    3. ...
    4. location: https://edition.cnn.com/politics
    5. ...
    7. HTTP/1.1 200 OK
    8. Content-Type: text/html; charset=utf-8
    9. ...
    10. Content-Length: 151654
    11. ...

    The output should be the same as in theTLS Origination for Egress Traffic example,without TLS origination.

    • Create an egress Gateway for edition.cnn.com, port 80, and a destination rule fortraffic directed to the egress gateway.

    Choose the instructions corresponding to whether or not you havemutual TLS Authentication enabled in Istio.

    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: Gateway
    4. metadata:
    5.   name: istio-egressgateway
    6. spec:
    7.   selector:
    8.     istio: egressgateway
    9.   servers:
    10.   - port:
    11.       number: 80
    12.       name: https
    13.       protocol: HTTPS
    14.     hosts:
    15.     - edition.cnn.com
    16.     tls:
    17.       mode: MUTUAL
    18.       serverCertificate: /etc/certs/cert-chain.pem
    19.       privateKey: /etc/certs/key.pem
    20.       caCertificates: /etc/certs/root-cert.pem
    21. ---
    22. apiVersion: networking.istio.io/v1alpha3
    23. kind: DestinationRule
    24. metadata:
    25.   name: egressgateway-for-cnn
    26. spec:
    27.   host: istio-egressgateway.istio-system.svc.cluster.local
    28.   subsets:
    29.   - name: cnn
    30.     trafficPolicy:
    31.       loadBalancer:
    32.         simple: ROUND_ROBIN
    33.       portLevelSettings:
    34.       - port:
    35.           number: 80
    36.         tls:
    37.           mode: ISTIO_MUTUAL
    38.           sni: edition.cnn.com
    39. EOF
    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: Gateway
    4. metadata:
    5.   name: istio-egressgateway
    6. spec:
    7.   selector:
    8.     istio: egressgateway
    9.   servers:
    10.   - port:
    11.       number: 80
    12.       name: http
    13.       protocol: HTTP
    14.     hosts:
    15.     - edition.cnn.com
    16. ---
    17. apiVersion: networking.istio.io/v1alpha3
    18. kind: DestinationRule
    19. metadata:
    20.   name: egressgateway-for-cnn
    21. spec:
    22.   host: istio-egressgateway.istio-system.svc.cluster.local
    23.   subsets:
    24.   - name: cnn
    25. EOF
    • Define a VirtualService to direct traffic from the sidecars to the egress gateway and from the egress gatewayto the external service:
    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: VirtualService
    4. metadata:
    5.   name: direct-cnn-through-egress-gateway
    6. spec:
    7.   hosts:
    8.   - edition.cnn.com
    9.   gateways:
    10.   - istio-egressgateway
    11.   - mesh
    12.   http:
    13.   - match:
    14.     - gateways:
    15.       - mesh
    16.       port: 80
    17.     route:
    18.     - destination:
    19.         host: istio-egressgateway.istio-system.svc.cluster.local
    20.         subset: cnn
    21.         port:
    22.           number: 80
    23.       weight: 100
    24.   - match:
    25.     - gateways:
    26.       - istio-egressgateway
    27.       port: 80
    28.     route:
    29.     - destination:
    30.         host: edition.cnn.com
    31.         port:
    32.           number: 80
    33.       weight: 100
    34. EOF
    • Resend the HTTP request to http://edition.cnn.com/politics.
    1. $ kubectl exec -it $SOURCE_POD -c sleep -- curl -sL -o /dev/null -D - http://edition.cnn.com/politics
    2. HTTP/1.1 301 Moved Permanently
    3. ...
    4. location: https://edition.cnn.com/politics
    5. ...
    7. HTTP/1.1 200 OK
    8. Content-Type: text/html; charset=utf-8
    9. ...
    10. Content-Length: 151654
    11. ...

    The output should be the same as in the step 2.

    • Check the log of the istio-egressgateway pod for a line corresponding to our request.If Istio is deployed in the istio-system namespace, the command to print the log is:
    1. $ kubectl logs -l istio=egressgateway -c istio-proxy -n istio-system | tail

    You should see a line similar to the following:

    1. [2019-09-03T20:57:49.103Z] "GET /politics HTTP/2" 301 - "-" "-" 0 0 90 89 "10.244.2.10" "curl/7.64.0" "ea379962-9b5c-4431-ab66-f01994f5a5a5" "edition.cnn.com" "151.101.65.67:80" outbound|80||edition.cnn.com - 10.244.1.5:80 10.244.2.10:50482 edition.cnn.com -

    Note that you only redirected the traffic from port 80 to the egress gateway. The HTTPS traffic to port 443went directly to edition.cnn.com.

    Cleanup HTTP gateway

    Remove the previous definitions before proceeding to the next step:

    1. $ kubectl delete gateway istio-egressgateway
    2. $ kubectl delete serviceentry cnn
    3. $ kubectl delete virtualservice direct-cnn-through-egress-gateway
    4. $ kubectl delete destinationrule egressgateway-for-cnn

    Egress gateway for HTTPS traffic

    In this section you direct HTTPS traffic (TLS originated by the application) through an egress gateway.You need to specify port 443 with protocol TLS in a corresponding ServiceEntry, an egress Gateway and a VirtualService.

    • Define a ServiceEntry for edition.cnn.com:
    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: ServiceEntry
    4. metadata:
    5.   name: cnn
    6. spec:
    7.   hosts:
    8.   - edition.cnn.com
    9.   ports:
    10.   - number: 443
    11.     name: tls
    12.     protocol: TLS
    13.   resolution: DNS
    14. EOF
    • Verify that your ServiceEntry was applied correctly by sending an HTTPS request to https://edition.cnn.com/politics.
    1. $ kubectl exec -it $SOURCE_POD -c sleep -- curl -sL -o /dev/null -D - https://edition.cnn.com/politics
    2. HTTP/1.1 200 OK
    3. Content-Type: text/html; charset=utf-8
    4. ...
    5. Content-Length: 151654
    6. ...
    • Create an egress Gateway for edition.cnn.com, a destination rule and a virtual serviceto direct the traffic through the egress gateway and from the egress gateway to the external service.

    Choose the instructions corresponding to whether or not you havemutual TLS Authentication enabled in Istio.

    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: Gateway
    4. metadata:
    5.   name: istio-egressgateway
    6. spec:
    7.   selector:
    8.     istio: egressgateway
    9.   servers:
    10.   - port:
    11.       number: 443
    12.       name: tls-cnn
    13.       protocol: TLS
    14.     hosts:
    15.     - edition.cnn.com
    16.     tls:
    17.       mode: MUTUAL
    18.       serverCertificate: /etc/certs/cert-chain.pem
    19.       privateKey: /etc/certs/key.pem
    20.       caCertificates: /etc/certs/root-cert.pem
    21. ---
    22. apiVersion: networking.istio.io/v1alpha3
    23. kind: DestinationRule
    24. metadata:
    25.   name: egressgateway-for-cnn
    26. spec:
    27.   host: istio-egressgateway.istio-system.svc.cluster.local
    28.   subsets:
    29.   - name: cnn
    30.     trafficPolicy:
    31.       loadBalancer:
    32.         simple: ROUND_ROBIN
    33.       portLevelSettings:
    34.       - port:
    35.           number: 443
    36.         tls:
    37.           mode: ISTIO_MUTUAL
    38.           sni: edition.cnn.com
    39. ---
    40. apiVersion: networking.istio.io/v1alpha3
    41. kind: VirtualService
    42. metadata:
    43.   name: direct-cnn-through-egress-gateway
    44. spec:
    45.   hosts:
    46.   - edition.cnn.com
    47.   gateways:
    48.   - mesh
    49.   - istio-egressgateway
    50.   tls:
    51.   - match:
    52.     - gateways:
    53.       - mesh
    54.       port: 443
    55.       sni_hosts:
    56.       - edition.cnn.com
    57.     route:
    58.     - destination:
    59.         host: istio-egressgateway.istio-system.svc.cluster.local
    60.         subset: cnn
    61.         port:
    62.           number: 443
    63.   tcp:
    64.   - match:
    65.     - gateways:
    66.       - istio-egressgateway
    67.       port: 443
    68.     route:
    69.     - destination:
    70.         host: edition.cnn.com
    71.         port:
    72.           number: 443
    73.       weight: 100
    74. EOF
    1. $ kubectl apply -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: Gateway
    4. metadata:
    5.   name: istio-egressgateway
    6. spec:
    7.   selector:
    8.     istio: egressgateway
    9.   servers:
    10.   - port:
    11.       number: 443
    12.       name: tls
    13.       protocol: TLS
    14.     hosts:
    15.     - edition.cnn.com
    16.     tls:
    17.       mode: PASSTHROUGH
    18. ---
    19. apiVersion: networking.istio.io/v1alpha3
    20. kind: DestinationRule
    21. metadata:
    22.   name: egressgateway-for-cnn
    23. spec:
    24.   host: istio-egressgateway.istio-system.svc.cluster.local
    25.   subsets:
    26.   - name: cnn
    27. ---
    28. apiVersion: networking.istio.io/v1alpha3
    29. kind: VirtualService
    30. metadata:
    31.   name: direct-cnn-through-egress-gateway
    32. spec:
    33.   hosts:
    34.   - edition.cnn.com
    35.   gateways:
    36.   - mesh
    37.   - istio-egressgateway
    38.   tls:
    39.   - match:
    40.     - gateways:
    41.       - mesh
    42.       port: 443
    43.       sni_hosts:
    44.       - edition.cnn.com
    45.     route:
    46.     - destination:
    47.         host: istio-egressgateway.istio-system.svc.cluster.local
    48.         subset: cnn
    49.         port:
    50.           number: 443
    51.   - match:
    52.     - gateways:
    53.       - istio-egressgateway
    54.       port: 443
    55.       sni_hosts:
    56.       - edition.cnn.com
    57.     route:
    58.     - destination:
    59.         host: edition.cnn.com
    60.         port:
    61.           number: 443
    62.       weight: 100
    63. EOF
    • Send an HTTPS request to https://edition.cnn.com/politics.The output should be the same as before.
    1. $ kubectl exec -it $SOURCE_POD -c sleep -- curl -sL -o /dev/null -D - https://edition.cnn.com/politics
    2. HTTP/1.1 200 OK
    3. Content-Type: text/html; charset=utf-8
    4. ...
    5. Content-Length: 151654
    6. ...
    • Check the log of the egress gateway’s proxy. If Istio is deployed in the istio-system namespace, the command toprint the log is:
    1. $ kubectl logs -l istio=egressgateway -n istio-system

    You should see a line similar to the following:

    1. [2019-01-02T11:46:46.981Z] "- - -" 0 - 627 1879689 44 - "-" "-" "-" "-" "151.101.129.67:443" outbound|443||edition.cnn.com 172.30.109.80:41122 172.30.109.80:443 172.30.109.112:59970 edition.cnn.com

    Cleanup HTTPS gateway

    1. $ kubectl delete serviceentry cnn
    2. $ kubectl delete gateway istio-egressgateway
    3. $ kubectl delete virtualservice direct-cnn-through-egress-gateway
    4. $ kubectl delete destinationrule egressgateway-for-cnn

    Additional security considerations

    Note that defining an egress Gateway in Istio does not in itself provides any special treatment for the nodeson which the egress gateway service runs. It is up to the cluster administrator or the cloud provider to deploythe egress gateways on dedicated nodes and to introduce additional security measures to make these nodes moresecure than the rest of the mesh.

    Istio cannot securely enforce that all egress traffic actually flows through the egress gateways. Istio onlyenables such flow through its sidecar proxies. If attackers bypass the sidecar proxy, they could directly accessexternal services without traversing the egress gateway. Thus, the attackers escape Istio’s control and monitoring.The cluster administrator or the cloud provider must ensure that no traffic leaves the mesh bypassing the egressgateway. Mechanisms external to Istio must enforce this requirement. For example, the cluster administratorcan configure a firewall to deny all traffic not coming from the egress gateway.The Kubernetes network policies canalso forbid all the egress traffic not originating from the egress gateway (seethe next section for an example).Additionally, the cluster administrator or the cloud provider can configure the network to ensure application nodes canonly access the Internet via a gateway. To do this, the cluster administrator or the cloud provider can prevent theallocation of public IPs to pods other than gateways and can configure NAT devices to drop packets not originating atthe egress gateways.

    Apply Kubernetes network policies

    This section shows you how to create aKubernetes network policy to preventbypassing of the egress gateway. To test the network policy, you create a namespace, test-egress, deploythe sleep sample to it, and then attempt to send requests to a gateway-securedexternal service.

    • Follow the steps in theEgress gateway for HTTPS traffic section.

    • Create the test-egress namespace:

    1. $ kubectl create namespace test-egress
    • Deploy the sleep sample to the test-egress namespace.

    Zip

    1. $ kubectl apply -n test-egress -f @samples/sleep/sleep.yaml@
    • Check that the deployed pod has a single container with no Istio sidecar attached:
    1. $ kubectl get pod $(kubectl get pod -n test-egress -l app=sleep -o jsonpath={.items..metadata.name}) -n test-egress
    2. NAME                     READY     STATUS    RESTARTS   AGE
    3. sleep-776b7bcdcd-z7mc4   1/1       Running   0          18m
    • Send an HTTPS request to https://edition.cnn.com/politics from the sleep pod inthe test-egress namespace. The request will succeed since you did not define any restrictive policies yet.
    1. $ kubectl exec -it $(kubectl get pod -n test-egress -l app=sleep -o jsonpath={.items..metadata.name}) -n test-egress -c sleep -- curl -s -o /dev/null -w "%{http_code}\n"  https://edition.cnn.com/politics
    2. 200
    • Label the namespaces where the Istio components (the control plane and the gateways) run.If you deployed the Istio components to istio-system, the command is:
    1. $ kubectl label namespace istio-system istio=system
    • Label the kube-system namespace.
    1. $ kubectl label ns kube-system kube-system=true
    • Define a NetworkPolicy to limit the egress traffic from the test-egress namespace to traffic destined toistio-system, and to the kube-system DNS service (port 53):
    1. $ cat <<EOF | kubectl apply -n test-egress -f -
    2. apiVersion: networking.k8s.io/v1
    3. kind: NetworkPolicy
    4. metadata:
    5.   name: allow-egress-to-istio-system-and-kube-dns
    6. spec:
    7.   podSelector: {}
    8.   policyTypes:
    9.   - Egress
    10.   egress:
    11.   - to:
    12.     - namespaceSelector:
    13.         matchLabels:
    14.           kube-system: "true"
    15.     ports:
    16.     - protocol: UDP
    17.       port: 53
    18.   - to:
    19.     - namespaceSelector:
    20.         matchLabels:
    21.           istio: system
    22. EOF
    • Resend the previous HTTPS request to https://edition.cnn.com/politics. Now itshould fail since the traffic is blocked by the network policy. Note that the sleep pod cannot bypassistio-egressgateway. The only way it can access edition.cnn.com is by using an Istio sidecar proxy and bydirecting the traffic to istio-egressgateway. This setting demonstrates that even if some malicious pod manages tobypass its sidecar proxy, it will not be able to access external sites and will be blocked by the network policy.
    1. $ kubectl exec -it $(kubectl get pod -n test-egress -l app=sleep -o jsonpath={.items..metadata.name}) -n test-egress -c sleep -- curl -v https://edition.cnn.com/politics
    2. Hostname was NOT found in DNS cache
    3.   Trying 151.101.65.67...
    4.   Trying 2a04:4e42:200::323...
    5. Immediate connect fail for 2a04:4e42:200::323: Cannot assign requested address
    6.   Trying 2a04:4e42:400::323...
    7. Immediate connect fail for 2a04:4e42:400::323: Cannot assign requested address
    8.   Trying 2a04:4e42:600::323...
    9. Immediate connect fail for 2a04:4e42:600::323: Cannot assign requested address
    10.   Trying 2a04:4e42::323...
    11. Immediate connect fail for 2a04:4e42::323: Cannot assign requested address
    12. connect to 151.101.65.67 port 443 failed: Connection timed out
    • Now inject an Istio sidecar proxy into the sleep pod in the test-egress namespace by first enablingautomatic sidecar proxy injection in the test-egress namespace:
    1. $ kubectl label namespace test-egress istio-injection=enabled
    • Then redeploy the sleep deployment:

    Zip

    1. $ kubectl delete deployment sleep -n test-egress
    2. $ kubectl apply -f @samples/sleep/sleep.yaml@ -n test-egress
    • Check that the deployed pod has two containers, including the Istio sidecar proxy (istio-proxy):
    1. $ kubectl get pod $(kubectl get pod -n test-egress -l app=sleep -o jsonpath={.items..metadata.name}) -n test-egress -o jsonpath='{.spec.containers[*].name}'
    2. sleep istio-proxy
    • Create the same destination rule as for the sleep pod in the default namespace to direct the traffic through the egress gateway:

    Choose the instructions corresponding to whether or not you havemutual TLS Authentication enabled in Istio.

    1. $ kubectl apply -n test-egress -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: DestinationRule
    4. metadata:
    5.   name: egressgateway-for-cnn
    6. spec:
    7.   host: istio-egressgateway.istio-system.svc.cluster.local
    8.   subsets:
    9.   - name: cnn
    10.     trafficPolicy:
    11.       loadBalancer:
    12.         simple: ROUND_ROBIN
    13.       portLevelSettings:
    14.       - port:
    15.           number: 443
    16.         tls:
    17.           mode: ISTIO_MUTUAL
    18.           sni: edition.cnn.com
    19. EOF
    1. $ kubectl apply -n test-egress -f - <<EOF
    2. apiVersion: networking.istio.io/v1alpha3
    3. kind: DestinationRule
    4. metadata:
    5.   name: egressgateway-for-cnn
    6. spec:
    7.   host: istio-egressgateway.istio-system.svc.cluster.local
    8.   subsets:
    9.   - name: cnn
    10. EOF
    • Send an HTTPS request to https://edition.cnn.com/politics. Now it should succeedsince the traffic flows to istio-egressgateway in the istio-system namespace, which is allowed by theNetwork Policy you defined. istio-egressgateway forwards the traffic to edition.cnn.com.
    1. $ kubectl exec -it $(kubectl get pod -n test-egress -l app=sleep -o jsonpath={.items..metadata.name}) -n test-egress -c sleep -- curl -s -o /dev/null -w "%{http_code}\n" https://edition.cnn.com/politics
    2. 200
    • Check the statistics of the egress gateway’s proxy and see a counter that corresponds to ourrequests to edition.cnn.com. If Istio is deployed in the istio-system namespace, the command to print thecounter is:
    1. $ kubectl exec $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') -c istio-proxy -n istio-system -- pilot-agent request GET stats | grep edition.cnn.com.upstream_cx_total
    2. cluster.outbound|443||edition.cnn.com.upstream_cx_total: 2

    Cleanup network policies

    • Delete the resources created in this section:

    Zip

    1. $ kubectl delete -f @samples/sleep/sleep.yaml@ -n test-egress
    2. $ kubectl delete destinationrule egressgateway-for-cnn -n test-egress
    3. $ kubectl delete networkpolicy allow-egress-to-istio-system-and-kube-dns -n test-egress
    4. $ kubectl label namespace kube-system kube-system-
    5. $ kubectl label namespace istio-system istio-
    6. $ kubectl delete namespace test-egress
    • Follow the steps in the Cleanup HTTPS gateway section.

    Troubleshooting

    • Check if you have mutual TLS Authentication enabled in Istio, following thesteps in Verify mutual TLS configuration.If mutual TLS is enabled, make sure you create the configurationitems accordingly (note the remarks If you have mutual TLS Authentication enabled in Istio, you must create…).

    • If mutual TLS Authentication is enabled, verify the correct certificate of theegress gateway:

    1. $ kubectl exec -i -n istio-system $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}')  -- cat /etc/certs/cert-chain.pem | openssl x509 -text -noout  | grep 'Subject Alternative Name' -A 1
    2.         X509v3 Subject Alternative Name:
    3.             URI:spiffe://cluster.local/ns/istio-system/sa/istio-egressgateway-service-account
    • For HTTPS traffic (TLS originated by the application), test the traffic flow by using the openssl command.openssl has an explicit option for setting the SNI, namely -servername.
    1. $ kubectl exec -it $SOURCE_POD -c sleep -- openssl s_client -connect edition.cnn.com:443 -servername edition.cnn.com
    2. CONNECTED(00000003)
    3. ...
    4. Certificate chain
    5.  0 s:/C=US/ST=California/L=San Francisco/O=Fastly, Inc./CN=turner-tls.map.fastly.net
    6.    i:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign CloudSSL CA - SHA256 - G3
    7.  1 s:/C=BE/O=GlobalSign nv-sa/CN=GlobalSign CloudSSL CA - SHA256 - G3
    8.    i:/C=BE/O=GlobalSign nv-sa/OU=Root CA/CN=GlobalSign Root CA
    9.  ---
    10.  Server certificate
    11.  -----BEGIN CERTIFICATE-----
    12. ...

    If you get the certificate as in the output above, your traffic is routed correctly. Check the statistics of the egress gateway’s proxy and see a counter that corresponds to your requests (sent by openssl and curl) to edition.cnn.com.

    1. $ kubectl exec $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') -c istio-proxy -n istio-system -- pilot-agent request GET stats | grep edition.cnn.com.upstream_cx_total
    2. cluster.outbound|443||edition.cnn.com.upstream_cx_total: 2

    Cleanup

    Shutdown the sleep service:

    Zip

    1. $ kubectl delete -f @samples/sleep/sleep.yaml@

    See also

    Secure Control of Egress Traffic in Istio, part 3

    Comparison of alternative solutions to control egress traffic including performance considerations.

    Secure Control of Egress Traffic in Istio, part 2

    Use Istio Egress Traffic Control to prevent attacks involving egress traffic.

    Secure Control of Egress Traffic in Istio, part 1

    Attacks involving egress traffic and requirements for egress traffic control.

    Egress Gateway Performance Investigation

    Verifies the performance impact of adding an egress gateway.

    Consuming External MongoDB Services

    Describes a simple scenario based on Istio's Bookinfo example.

    Monitoring and Access Policies for HTTP Egress Traffic

    Describes how to configure Istio for monitoring and access policies of HTTP egress traffic.