-
Notifications
You must be signed in to change notification settings - Fork 5
Remove device from Tailnet #3
Comments
You can also use ephemeral nodes when you create auth keys. Nodes are automatically pruned from your Tailnet after some period of inactivity. |
Problem with this is that I want to retain the service's IP address |
I'm relatively new to Tailscale as a product offering, how do you persist the IP address between different deployments? This is one of my concerns, albeit less so as we're using external-dns to sync ts-* services to our DNS provider. |
Tailscaled stores it's state (including the machinekey / Tailnet device registration) in a Kubernetes secret. |
I feel like deleting the service should trigger deleting + cleaning up the host on your tailnet. If people want explicit ips to be set on their LBs, they should have to set that via an annotation, or they should do it like metal LB does it with a spec.loadBalancerIP field. If this design sounds good, I don't mind implementing it when I have some time. |
This is the same thing I've got in mind. Although I don't know if it's possible to set your own loadBalancerIP. |
Right now when you delete the service, it will leave behind a device in your Tailnet that has to be manually removed.
This can technically be automated using the Tailscale API.
The text was updated successfully, but these errors were encountered: