mirror of https://github.com/istio/istio.io.git
change the name of the Envoy's container in egress gateway (#2896)
egressgateway -> istio-proxy
This commit is contained in:
parent
45438c46f3
commit
de3d56dd81
|
|
@ -243,7 +243,7 @@ be done by the egress gateway, as opposed to by the sidecar in the previous exam
|
||||||
If Istio is deployed in the `istio-system` namespace, the command to print the log is:
|
If Istio is deployed in the `istio-system` namespace, the command to print the log is:
|
||||||
|
|
||||||
{{< text bash >}}
|
{{< text bash >}}
|
||||||
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') egressgateway -n istio-system | tail
|
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') istio-proxy -n istio-system | tail
|
||||||
{{< /text >}}
|
{{< /text >}}
|
||||||
|
|
||||||
You should see a line similar to the following:
|
You should see a line similar to the following:
|
||||||
|
|
|
||||||
|
|
@ -253,7 +253,7 @@ First create a `ServiceEntry` to allow direct traffic to an external service.
|
||||||
If Istio is deployed in the `istio-system` namespace, the command to print the log is:
|
If Istio is deployed in the `istio-system` namespace, the command to print the log is:
|
||||||
|
|
||||||
{{< text bash >}}
|
{{< text bash >}}
|
||||||
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') egressgateway -n istio-system | tail
|
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') istio-proxy -n istio-system | tail
|
||||||
{{< /text >}}
|
{{< /text >}}
|
||||||
|
|
||||||
You should see a line similar to the following:
|
You should see a line similar to the following:
|
||||||
|
|
|
||||||
|
|
@ -225,7 +225,7 @@ Istio 0.8 引入了 [Ingress 和 Egress gateway](/zh/docs/reference/config/istio
|
||||||
1. 检查 `istio-egressgateway` pod 的日志,并查看与我们的请求对应的行。如果 Istio 部署在 `istio-system` 命名空间中,则打印日志的命令是:
|
1. 检查 `istio-egressgateway` pod 的日志,并查看与我们的请求对应的行。如果 Istio 部署在 `istio-system` 命名空间中,则打印日志的命令是:
|
||||||
|
|
||||||
{{< text bash >}}
|
{{< text bash >}}
|
||||||
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') egressgateway -n istio-system | tail
|
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') istio-proxy -n istio-system | tail
|
||||||
{{< /text >}}
|
{{< /text >}}
|
||||||
|
|
||||||
我们看到与请求相关的行,类似于以下内容:
|
我们看到与请求相关的行,类似于以下内容:
|
||||||
|
|
@ -432,7 +432,7 @@ $ kubectl delete destinationrule egressgateway-for-cnn
|
||||||
1. 检查 `istio-egressgateway` pod 的日志,并查看与我们的请求相对应的行。如果 Istio 部署在 `istio-system` 命名空间中,则打印日志的命令是:
|
1. 检查 `istio-egressgateway` pod 的日志,并查看与我们的请求相对应的行。如果 Istio 部署在 `istio-system` 命名空间中,则打印日志的命令是:
|
||||||
|
|
||||||
{{< text bash >}}
|
{{< text bash >}}
|
||||||
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') egressgateway -n istio-system | tail
|
$ kubectl logs $(kubectl get pod -l istio=egressgateway -n istio-system -o jsonpath='{.items[0].metadata.name}') istio-proxy -n istio-system | tail
|
||||||
{{< /text >}}
|
{{< /text >}}
|
||||||
|
|
||||||
这里会看到与之前请求相关的行,类似于以下内容:
|
这里会看到与之前请求相关的行,类似于以下内容:
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue