Skip to content
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.

Remove device from Tailnet #3

Open
clrxbl opened this issue Jun 14, 2022 · 6 comments
Open

Remove device from Tailnet #3

clrxbl opened this issue Jun 14, 2022 · 6 comments

Comments

@clrxbl
Copy link
Owner

clrxbl commented Jun 14, 2022

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.

@jakedgy
Copy link

jakedgy commented Jun 14, 2022

You can also use ephemeral nodes when you create auth keys. Nodes are automatically pruned from your Tailnet after some period of inactivity.

@clrxbl
Copy link
Owner Author

clrxbl commented Jun 14, 2022

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

@bbetter173
Copy link
Contributor

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.

@clrxbl
Copy link
Owner Author

clrxbl commented Aug 1, 2022

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.

@devinbedari
Copy link

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.

@clrxbl
Copy link
Owner Author

clrxbl commented Oct 27, 2022

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants