Skip to content

Add connector + Envoy design doc#556

Open
zachsmith1 wants to merge 4 commits intomainfrom
feat/connector-envoy
Open

Add connector + Envoy design doc#556
zachsmith1 wants to merge 4 commits intomainfrom
feat/connector-envoy

Conversation

@zachsmith1
Copy link
Contributor

Adds a new connector/Envoy design doc for datum-connect/datum-desktop, detailing the end-to-end tunnel flow, sidecar metadata contract, and NSO programming responsibilities. It documents three Envoy Gateway implementation options with diagrams and validation notes, and clarifies MVP scope as CONNECT-TCP with a path to CONNECT-UDP. Open questions include which Envoy Gateway option to standardize on and whether to define an initial ConnectorClass (its intention and how it should work).

@zachsmith1
Copy link
Contributor Author

@joshlreese please review when you have a second

Copy link

@Frando Frando left a comment

Choose a reason for hiding this comment

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

A couple of comments inline. On initial read, I don't see the doc describing the step how your control plane actually configures envoy (or how envoy fetches out to the control plane) so that envoy can map an incoming request's domain name to a connector + advertisment so that it can inject the correct headers when forwarding to the iroh sidecar.

On the details of the different ways to configure envoy with internal listeners for forwarding I can't comment much due to lack of experience with deploying envoy.

@zachsmith1 zachsmith1 force-pushed the feat/connector-envoy branch from 7d81e88 to 4109ee7 Compare January 20, 2026 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants