Skip to content

chore: add support for peer updates to tailnet.configMaps #11487

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 11, 2024

Conversation

spikecurtis
Copy link
Contributor

Adds support to configMaps to handle peer updates including lost and disconnected peers

Copy link
Contributor Author

spikecurtis commented Jan 8, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @spikecurtis and the rest of your teammates on Graphite Graphite

@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-initial branch from 032d52d to b03a760 Compare January 9, 2024 08:10
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch from d744013 to 76ec6f7 Compare January 9, 2024 08:10
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-initial branch from b03a760 to 6f37b9b Compare January 9, 2024 11:37
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch from 76ec6f7 to 2baf90f Compare January 9, 2024 11:37
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch from 2baf90f to 3844f8a Compare January 10, 2024 04:58
@spikecurtis spikecurtis requested a review from coadler January 10, 2024 04:59
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-initial branch from 6f37b9b to 0ec3722 Compare January 10, 2024 06:10
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch from 3844f8a to e01bbcf Compare January 10, 2024 06:14
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-initial branch 2 times, most recently from d013264 to 018e3b8 Compare January 10, 2024 06:51
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch from e01bbcf to a02de8b Compare January 10, 2024 06:51
Base automatically changed from spike/10533-configmaps-initial to main January 10, 2024 06:58
@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch 2 times, most recently from 40c72c2 to 3b8d264 Compare January 10, 2024 11:55
var lastHandshake time.Time
if ps, ok := status.Peer[node.Key]; ok {
lastHandshake = ps.LastHandshake
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a situation a peer would be missing from the configMaps peer list but still be in the engine's peer list?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, immediately after receiving a DISCONNECTED update, we remove it from configMaps. Then until the next update it'll be in the engine but not configMaps. Probably an edge case for us to DISCONNECT and then immediately get a new NODE update, though.

// Then: we don't configure
requireNeverConfigures(ctx, t, uut)

p1ID := uuid.MustParse("10000000-0000-0000-0000-000000000000")
Copy link
Contributor

Choose a reason for hiding this comment

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

A nice shorthand for this is uuid.UUID{1}

@spikecurtis spikecurtis force-pushed the spike/10533-configmaps-peerupdates branch from 3b8d264 to b573a10 Compare January 11, 2024 05:01
@spikecurtis spikecurtis merged commit 617ecbf into main Jan 11, 2024
@spikecurtis spikecurtis deleted the spike/10533-configmaps-peerupdates branch January 11, 2024 05:11
Copy link
Contributor Author

Merge activity

@github-actions github-actions bot locked and limited conversation to collaborators Jan 11, 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.

2 participants