Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix images and nav issues #6230

Merged
merged 1 commit into from
Feb 21, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/zh/docs/network/images/egress-check.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/zh/docs/network/images/new-vm.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 5 additions & 1 deletion docs/zh/docs/network/modules/egressgateway/failover.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,17 +66,21 @@ status:

EgressGateway Agent 会通过 `feature.tunnelUpdatePeriod` 间隔定时更新 `status.lastHeartbeatTime` 字段,EgressGateway Controller 则会通过 `feature.tunnelMonitorPeriod` 定时列出所有 EgressTunnel,分别检查 `status.lastHeartbeatTime` 与 `feature.eipEvictionTimeout` 的和是否超过当前时间。

![egress-check](./egress-check.svg)
![egress-check](../../images/egress-check.svg)

Datapath Failover 问题排查步骤:

1. 首先,查看 EgressGateway 应用的安装配置文件 `values.yaml`,确认与 Datapath Failover 相关的配置是否设置合理,特别是确保 `eipEvictionTimeout` 的值大于 `tunnelMonitorPeriod` 加上 `tunnelUpdatePeriod` 的总和;
2. 执行 `kubectl get egt -w` 命令,检查 `EgressTunnel` 的状态。检查选中的 Node 是否处于 `HeartbeatTimeout` 状态,并且是否存在其他处于 `Ready` 状态的 `EgressTunnel`;

```shell
kubectl get egt -w
```
```
NAME TUNNELMAC TUNNELIPV4 TUNNELIPV6 MARK PHASE
node1 66:50:85:cb:b2:bf 192.200.229.11 fd01::c486 0x26d9b723 Ready
node2 66:d4:65:85:e2:c7 192.200.128.75 fd01::6676 0x26abf380 HeartbeatTimeout
node3 66:c4:da:a7:58:25 192.200.101.153 fd01::edb5 0x26c4ce84 Ready
```

3. 如果想查询是否出现过 HeartbeatTimeout 导致的 IP 切换,可以在 controller 容器检索 `update tunnel status to HeartbeatTimeout` 相关的日志。
5 changes: 5 additions & 0 deletions docs/zh/docs/network/modules/egressgateway/install.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,8 @@
---
hide:
- toc
---

# 安装 EgressGateway

本章节主要介绍如何安装 EgressGateway 组件。
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ default egressgateway-controller-6cd86df57-xm2d4 1/1 Running 0 86m

我们新创建一台机器,作为 VPC 网络东西向的服务器,在这里我启动的机器 IP 为 `172.17.81.29`。

![new-vm](./new-vm.png)
![new-vm](../../../images/new-vm.png)

运行下面命令启动测试服务器,他的功能是 `curl ip:8080`,它会返回客户端的 IP 地址,可以供我们检查 Egress IP 运作是否正常。

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,9 @@
EgressGateway 使用了 vxlan 隧道,经过测试 vxlan 损耗在 10% 左右。如果您发现 EgressGateway 的速度不达标,可以执行如下步骤检查:

1. 确认宿主机节点到节点的速度符合预期;
1. vxlan 使用的宿主机的网卡的 offload 设置会对 vxlan 接口的速度产生较小的影响(在 10G 网卡测试中仅会有 0.5 Gbits/sec 的差距),可以执行 `ethtool --offload host-interface-name rx on tx on` 开启 offload。

vxlan 使用的宿主机的网卡的 offload 设置会对 vxlan 接口的速度产生较小的影响(在 10G 网卡测试中仅会有 0.5 Gbits/sec 的差距),可以执行 `ethtool --offload host-interface-name rx on tx on` 开启 offload。

2. vxlan 网卡的 offload 设置可以对 vxlan 接口速度产生较大的影响(在 10G 网卡测试中,不开启 2.5 Gbits/sec,开启 8.9 Gbits/sec),你可以运行 `ethtool -k egress.vxlan` 检查 checksum offload 是否关闭,并通过 helm values 的配置 `feature.vxlan.disableChecksumOffload` 为 `false` 开启 offload。

### Benchmark
Expand All @@ -24,7 +26,7 @@ EgressGateway 使用了 vxlan 隧道,经过测试 vxlan 损耗在 10% 左右
| case2 | egress vxlan -> egress vxlan | `9.11 Gbits/sec sender - 9.09 Gbits/sec receiver` |
| case3 | pod -> egress node -> target | `9.01 Gbits/sec sender - 8.98 Gbits/sec receiver` |

![egress-check](../images/speed.svg)
![egress-check](../../images/speed.svg)

#### 虚拟机

Expand All @@ -41,4 +43,4 @@ EgressGateway 使用了 vxlan 隧道,经过测试 vxlan 损耗在 10% 左右
|:------|:-----------------------------|:--------------------------------------------------|
| case1 | node -> node | `2.99 Gbits/sec sender - 2.99 Gbits/sec receiver` |
| case2 | egress vxlan -> egress vxlan | `1.73 Gbits/sec sender - 1.71 Gbits/sec receiver` |
| case3 | pod -> egress node -> target | `1.23 Gbits/sec sender - 1.22 Gbits/sec receiver` |
| case3 | pod -> egress node -> target | `1.23 Gbits/sec sender - 1.22 Gbits/sec receiver` |
Loading