Skip to content

feat: promote single-tailnet out of experimental #11366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

spikecurtis
Copy link
Contributor

Single tailnet is no longer experimental

Copy link
Contributor Author

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

@spikecurtis spikecurtis force-pushed the spike/single-tailnet-experimental branch from d9ae78d to 7fc5315 Compare January 3, 2024 05:08
@bpmct
Copy link
Member

bpmct commented Jan 3, 2024

Silly question, but single tailnet is different than tailnet v2, right?

Copy link
Contributor

@coadler coadler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛥️

@spikecurtis
Copy link
Contributor Author

Silly question, but single tailnet is different than tailnet v2, right?

Yeah, single tailnet is a performance optimization to get better memory utilization when Coderd proxies connections to workspaces.

Tailnet v2 is an upgrade to the coordination protocol to allow for things like explicit disconnects, & API versioning.

@spikecurtis spikecurtis merged commit 48cd4c3 into main Jan 4, 2024
@spikecurtis spikecurtis deleted the spike/single-tailnet-experimental branch January 4, 2024 05:27
@github-actions github-actions bot locked and limited conversation to collaborators Jan 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants