Skip to content
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

tailcfg: document peer node capability #11379

Closed
wants to merge 2 commits into from

Conversation

clairew
Copy link
Member

@clairew clairew commented Mar 8, 2024

Updates tailscale/corp#17516

@clairew clairew requested a review from a team as a code owner March 8, 2024 19:11
@clairew clairew force-pushed the clairew/peer-node-capability-documentation branch from 282863a to 53e0a6a Compare March 8, 2024 19:13
Updates tailscale/corp#17516

Signed-off-by: Claire Wang <claire@tailscale.com>
Comment on lines 329 to 331
// CapMap and Capabilities are both ways for control to send metadata about a peer node.
// By accessing a self node's peers - a self node can check the peer's capabilities.
// Capabilities can be used to label information about a peer.
Copy link
Member

Choose a reason for hiding this comment

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

I think the docs for how to use new functionality should probably be added to the new thing instead.

"A self node's peers" is awkward to say and doesn't really reflect how MapResponse is setup (also this file does not mention "self node") -- there is Peers, which is a slice of Nodes, and there is Self, which is also a Node.

Change-Id: Iad2dafb38ffb9948bc2f3dfaf9c268f7d772cf56
Signed-off-by: Adrian Dewhurst <adrian@tailscale.com>
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.

None yet

2 participants