Stewart Thomson
Stewart Thomson
I'm going to take a crack at adding this, if that's OK
We see this occasionally as well. Normally restarting the headscale instance a couple of times fixes it. This only happens after we update the routes of a subnet router, and...
 Here are the logs on headscale's side regarding the particular node
I wonder if it's an issue of awkward timing where a machine is declared to be offline while it is trying to authenticate
Some info on timing: At 2024-04-04 10:14:50.000 headscale reports "Machine successfully authorized" At 2024-04-04 10:14:51.000 headscale reports "Machine successfully authorized" At 2024-04-04T14:14:51.078128612Z subnet router node reports "RegisterReq: got response; nodeKeyExpired=false,...
We are seeing this on 0.22.3. Not sure if it's a coincidence, but a lot of our users upgraded their tailscale clients from 1.56.x client to 1.58.x today
I'll also mention that this seems to occur after we restart our headscale deployment in kubernetes. I imagine that any brief overlap between pod uptimes may be the cause of...
We're currently switching to using a Statefulset instead of a Deployment (should've done that in the first place) to address the overlap. Postgres is a good idea, we'll do that...
You'll need to bump controller-gen to 0.14.0 in the makefile
Bit of an old issue, but it would also be good to have this for AutoscalingRunnerSet resources as well