[GH-ISSUE #4727] [Feature Request] 如何在 k8s 集群上启用多副本后实现 frps 管理的 frpc 连接信息同步？

gitea-mirror commented

2026-05-05 14:23:30 -06:00

Owner

Copy link

Originally created by @jiekechoo on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4727

Describe the feature request

我已经在 k8s 集群上部署了 frps 多副本，使用 NodePort 或 LoadBalancer 模式对外提供服务，当 frpc 1 连接/注册到某个 frps 1 时，访问者通过 frpc1.a.com 访问时，k8s 可能就路由到 frps 2 上，这时候，如何同步 frps 1 的连接信息到 frps 2?
这样，是不是就可以实现服务端的负载均衡？达到高可用和弹性伸缩？

Describe alternatives you've considered

No response

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @jiekechoo on GitHub (Mar 25, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4727 ### Describe the feature request 我已经在 k8s 集群上部署了 frps 多副本，使用 NodePort 或 LoadBalancer 模式对外提供服务，当 frpc 1 连接/注册到某个 frps 1 时，访问者通过 frpc1.a.com 访问时，k8s 可能就路由到 frps 2 上，这时候，如何同步 frps 1 的连接信息到 frps 2? 这样，是不是就可以实现服务端的负载均衡？达到高可用和弹性伸缩？ ### Describe alternatives you've considered _No response_ ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [x] Developer Infrastructure - [ ] Client Plugin - [x] Server Plugin - [x] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:23:30 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:23:33 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 9, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Apr 9, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror commented

2026-05-05 14:23:33 -06:00

Author

Owner

Copy link

@jiekechoo commented on GitHub (Apr 9, 2025):

@fatedier 这个有什么办法吗？

@jiekechoo commented on GitHub (Apr 9, 2025): @fatedier 这个有什么办法吗？

gitea-mirror commented

2026-05-05 14:23:33 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 24, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Apr 24, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:49:24 -06:00

[PR #3740] [MERGED] frpc: exit with code 1 if first login failed #4823

No Branch/Tag specified