You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gateways: Edge gateway should handle automatic closure of tunnel after timer expiration #1809
Currently the central manager handles tunnel expiration timers and the closure of the tunnels but this should be handled by the edge gateway for robustness.
We need to have a migration strategy for this and we should potentially include a version in the GatewayCapabilitiesResponseEvent so that the central instance can know if the edge gateway supports managing timeouts itself.
Idea is to move the timeout logic that is in GatewayService and calls GatewayConnector.closeTunnel() to the edge gateway itself but we should also ensure that backwards compatibility is maintained (log at WARN when an older version edge gateway connects).
Activity
richturner commentedon Oct 1, 2025
We need to have a migration strategy for this and we should potentially include a version in the
GatewayCapabilitiesResponseEventso that the central instance can know if the edge gateway supports managing timeouts itself.Idea is to move the timeout logic that is in
GatewayServiceand callsGatewayConnector.closeTunnel()to the edge gateway itself but we should also ensure that backwards compatibility is maintained (log at WARN when an older version edge gateway connects).