istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[zh]: fix locality-load-balancing/failover/index.md link fail (#12273) 

Signed-off-by: aimuz <mr.imuz@gmail.com>

Signed-off-by: aimuz <mr.imuz@gmail.com>
This commit is contained in:
aimuz 2022-11-22 00:53:57 +08:00 committed by GitHub
parent f61706a5f4
commit 786a00a399
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/zh/docs/tasks/traffic-management/locality-load-balancing/failover/index.md
View File

@ -63,7 +63,7 @@ spec:
EOF
{{< /text >}}
## 验证流量保持在 `region1.zone1` {#verify-traffic-stays-in-`region1.zone1`}
## 验证流量保持在 `region1.zone1` {#verify-traffic-stays-in-region1zone1}
从 `sleep` Pod 调用 `helloWorld` 服务：
@ -79,7 +79,7 @@ Hello version: region1.zone1, instance: helloworld-region1.zone1-86f77cd7b-cpxhv
重复几次，验证响应总是相同的。
## 故障转移到 `region1.zone2` {#failover-to-`region1.zone2`}
## 故障转移到 `region1.zone2` {#failover-to-region1zone2}
接下来， 触发故障转移到 `region1.zone2`。为此，您在 `region1.zone1` 中 `helloWorld` [逐出 Envoy Sidecar 代理](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/draining#draining) ：
@ -102,7 +102,7 @@ Hello version: region1.zone2, instance: helloworld-region1.zone2-86f77cd7b-cpxhv
第一个调用将失败，这将触发故障转移。多次重复该命令，并验证响应中的 `version` 始终为 `region1.zone2`。
## 故障转移到 `region2.zone3` {#failover-to-`region2.zone3`}
## 故障转移到 `region2.zone3` {#failover-to-region2zone3}
现在触发故障转移到 `region2.zone3`。正如您之前所做的，配置 `helloWorld` 在 `region1.zone2` 中调用失败。
@ -125,7 +125,7 @@ Hello version: region2.zone3, instance: helloworld-region2.zone3-86f77cd7b-cpxhv
第一个调用将失败，这将触发故障转移。多次重复该命令，并验证响应中的 `version` 始终为 `region2.zone3`。
## 故障转移到 `region3.zone4` {#failover-to-`region3.zone4`}
## 故障转移到 `region3.zone4` {#failover-to-region3zone4}
现在触发故障转移到 `region3.zone4`。正如您之前所做的， 配置 `helloWorld` 在 `region2.zone3` 中调用失败。