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

implement selfupdate and pass expiry #1647

Merged
merged 4 commits into from
Jan 5, 2024

Conversation

kradalby
Copy link
Collaborator

@kradalby kradalby commented Dec 10, 2023

Currently we support informing nodes upon change, but do not have a mechanism for updating the node from control and down.

This commits add a SelfUpdate state change and it is used to inform a node if it keys has been expired control side.

This PR makes 1.36 the last supported version as it exposes keyexpiry information.

fixes #1645

@kradalby kradalby added this to the v0.23.0 milestone Dec 11, 2023
Currently we support informing nodes upon change, but do not
have a mechanism for updating the node from control and down.

This commits add a SelfUpdate state change, which allows this.

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
@kradalby kradalby marked this pull request as ready for review January 3, 2024 17:08
@kradalby kradalby requested a review from juanfont as a code owner January 3, 2024 17:08
This commit makes sure node expiry is propagated to
the nodes immediatly when a node expiry even occurs
and verifies this with integration tests.

In addition, it removes old logic for filtering out
expired nodes from the netmap, this is not how Tailscale
SaaS does it, and we should follow the same approach.

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
@kradalby kradalby removed this from the v0.23.0 milestone Jan 4, 2024
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
@kradalby kradalby merged commit 3b10328 into juanfont:main Jan 5, 2024
46 checks passed
@kradalby kradalby deleted the propogate-expiry branch January 5, 2024 09:41
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.

Expiry information does not seem to be propagated correctly
2 participants