[Feature Request] loopLoginUntilSuccess Flag in ClientCommonConfig to decide to keep retrying to connect to server or exit

[smodhave]

Describe the feature request

I’m working on a project where I need multiple Kubernetes pods with FRP clients for high availability, but only one should be connected to the server by acquiring a lease. These pods are distributed across different availability zones.

There might be scenarios where the network in the availability zone of the pod that has acquired the lease goes down. In such cases, the FRP client will retry indefinitely, and the pod will not be able to release the lease because no error is thrown.

Additionally, there could be other situations where the user needs to take control and implement their own logic before retrying the connection if necessary.

Describe alternatives you've considered

Instead of loopLoginUntilSuccess flag, we can also have maxLoginRetries attribute.

Affected area

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

[fatedier]

I don’t think this is the right way. You usually need to redesign your entire architecture to solve the problem.