rosstimothy 6cb13715ba Dynamically resolve reverse tunnel address (#9958) ...

* Dynamically resolve reverse tunnel address

The reverse tunnel address is currently a static string that is
retrieved from config and passed around for the duration of a
services lifetime. When the `tunnel_public_address` is changed
on the proxy and the proxy is then restarted, all established
reverse tunnels over the old address will fail indefinintely.
As a means to get around this, #8102 introduced a mechanism
that would cause nodes to restart if their connection to the
auth server was down for a period of time. While this did
allow the nodes to pickup the new address after the nodes
restarted it was meant to be a stop gap until a more robust
solution could be applid.

Instead of using a static address, the reverse tunnel address
is now resolved via a `reversetunnel.Resolver`. Anywhere that
previoulsy relied on the static proxy address now will fetch
the actual reverse tunnel address via the webclient by using
the Resolver. In addition this builds on the refactoring done
in #4290 to further simplify the reversetunnel package. Since
we no longer track multiple proxies, all the left over bits
that did so have been removed to accomodate using a dynamic
reverse tunnel address.

2022-02-03 16:24:48 +00:00

..

doc.go

cache event fanout & reversetunnel improvements

2020-04-23 14:03:52 -07:00

workpool_test.go

Dynamically resolve reverse tunnel address (#9958)

2022-02-03 16:24:48 +00:00

workpool.go

Dynamically resolve reverse tunnel address (#9958)

2022-02-03 16:24:48 +00:00