mirror of https://github.com/istio/istio.io.git
Minor egress fixes (#5025)
* fix the protocol in an HTTPS URL * add "Enable Envoy's Access Logging" step to egress tasks
This commit is contained in:
parent
06f78cf400
commit
28db342298
|
|
@ -45,6 +45,8 @@ traffic to external services.
|
|||
|
||||
* [Deploy Istio egress gateway](/docs/tasks/traffic-management/egress/egress-gateway/#deploy-istio-egress-gateway).
|
||||
|
||||
* [Enable Envoy’s access logging](/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging)
|
||||
|
||||
## Perform TLS origination with an egress gateway
|
||||
|
||||
This section describes how to perform the same TLS origination as in the
|
||||
|
|
|
|||
|
|
@ -37,6 +37,8 @@ controlled way.
|
|||
|
||||
{{< boilerplate before-you-begin-egress >}}
|
||||
|
||||
* [Enable Envoy’s access logging](/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging)
|
||||
|
||||
## Deploy Istio egress gateway
|
||||
|
||||
1. Check if the Istio egress gateway is deployed:
|
||||
|
|
@ -310,7 +312,7 @@ You need to specify port 443 with protocol `TLS` in a corresponding `ServiceEntr
|
|||
EOF
|
||||
{{< /text >}}
|
||||
|
||||
1. Verify that your `ServiceEntry` was applied correctly by sending an HTTPS request to [http://edition.cnn.com/politics](https://edition.cnn.com/politics).
|
||||
1. Verify that your `ServiceEntry` was applied correctly by sending an HTTPS request to [https://edition.cnn.com/politics](https://edition.cnn.com/politics).
|
||||
|
||||
{{< text bash >}}
|
||||
$ kubectl exec -it $SOURCE_POD -c sleep -- curl -sL -o /dev/null -D - https://edition.cnn.com/politics
|
||||
|
|
@ -482,7 +484,7 @@ You need to specify port 443 with protocol `TLS` in a corresponding `ServiceEntr
|
|||
|
||||
{{< /tabset >}}
|
||||
|
||||
1. Send an HTTPS request to [http://edition.cnn.com/politics](https://edition.cnn.com/politics).
|
||||
1. Send an HTTPS request to [https://edition.cnn.com/politics](https://edition.cnn.com/politics).
|
||||
The output should be the same as before.
|
||||
|
||||
{{< text bash >}}
|
||||
|
|
|
|||
|
|
@ -15,6 +15,8 @@ example extends that example to show how to configure SNI monitoring and apply p
|
|||
|
||||
* [Deploy Istio egress gateway](/docs/tasks/traffic-management/egress/egress-gateway/#deploy-istio-egress-gateway).
|
||||
|
||||
* [Enable Envoy’s access logging](/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging)
|
||||
|
||||
* Configure traffic to `*.wikipedia.org` by following
|
||||
[the steps](/docs/tasks/traffic-management/egress/wildcard-egress-hosts/#wildcard-configuration-for-arbitrary-domains) in
|
||||
[Configure Egress Traffic using Wildcard Hosts](/docs/tasks/traffic-management/egress/wildcard-egress-hosts/) example,
|
||||
|
|
|
|||
|
|
@ -18,6 +18,8 @@ services.
|
|||
|
||||
{{< boilerplate before-you-begin-egress >}}
|
||||
|
||||
* [Enable Envoy’s access logging](/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging)
|
||||
|
||||
## Deploy an HTTPS proxy
|
||||
|
||||
To simulate a legacy proxy and only for this example, you deploy an HTTPS proxy inside your cluster.
|
||||
|
|
|
|||
|
|
@ -25,6 +25,8 @@ without the need to specify every language's site separately.
|
|||
|
||||
* [Deploy Istio egress gateway](/docs/tasks/traffic-management/egress/egress-gateway/#deploy-istio-egress-gateway).
|
||||
|
||||
* [Enable Envoy’s access logging](/docs/tasks/observability/logs/access-log/#enable-envoy-s-access-logging)
|
||||
|
||||
## Configure direct traffic to a wildcard host
|
||||
|
||||
The first, and simplest, way to access a set of hosts within a common domain is by configuring
|
||||
|
|
|
|||
Loading…
Reference in New Issue