Skip to content

enhance tailnetAPIConnector to support multiple peers #14729

@spikecurtis

Description

@spikecurtis

Right now, the tailnetAPIConnector used for client connections only supports a single peer (a workspace Agent), specified at instantiation. For the use case of a native desktop VPN, we need to support multiple peers that can be added and removed as workspaces are started and stopped.

In implementing this, we should consider refactoring to share code between servertailnet and tailnetAPIConnector, both of which need to support multiple Agent peers.

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions