Closed dboslee closed 2 years ago
@dboslee can you remind me why this is necessary?
@dboslee can you remind me why this is necessary?
@NajiObeid I think this is mostly to be consistent with how other addresses are configurable in teleport. The use case would be for listening on a specific address with peer_listen_addr: 10.0.0.1:3021
but then setting some domainpeer_public_addr: example.teleport.com
for peers to dial.
The grpc load balancing comment was just a thought on how it could be implemented. Maybe its enough to allow a single addr and nothing really needs to change for the proxy peer client.
What
Based on this discussion.
How
This will need to be added to the
ServerSpec
to be stored in the backend and distributed to peer proxies.Other
_public_addr
configuration fields support lists. If we intend to support a list forpeer_public_addr
the proxy peering client will need to support dialing to the list of addresses and load balancing between them. See grpc/balancer for details on grpc client load balancing.