Skip to content

Commit efc8bad

Browse files
authored
Update 03-special-environment-deployment.md
1 parent 4c5d66a commit efc8bad

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/zh/04-best-practice/03-special-environment-deployment.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -385,3 +385,19 @@ setcap -r /usr/sbin/deepflow-agent
385385
rmdir /sys/fs/cgroup/cpu/deepflow-agent
386386
rmdir /sys/fs/cgroup/memory/deepflow-agent
387387
```
388+
389+
# Agent 通过 LB 访问 Server
390+
391+
## agent 与 server 集群间网络受限,需通过 lb 连接
392+
393+
当多套 k8s 集群间网络无法互通时,deepflow-agent 可通过 LB 连接 deepflow-server。默认情况下 deepflow-server 的 Service 类型为 NodePort,需在 LB 配置两个端口转发至后端服务器的:30033(用于 agent 注册)和 30035(用于 agent 数据上报),并在 agent-group-config 中添加对应 LB 地址和端口:
394+
> 注:除网络隔离等特殊情况外,不建议使用 LB 接入方案。默认机制下,agent 会根据数据量自动选择 server 节点,实现动态负载均衡;而通过 LB 接入时,数据上报路径将受限于 LB 的负载策略,会导致 server 节点负载不均。
395+
396+
```yaml
397+
global:
398+
communication:
399+
ingester_port: $LB_PORT
400+
proxy_controller_port: $LB_PORT
401+
ingester_ip: $LB_IP
402+
proxy_controller_ip: $LB_IP
403+
```

0 commit comments

Comments
 (0)