

Or later, when the device exits, the tailscaled daemon itself performs tailscale logout which immediately removes the device from your tailnet.

For example, you can add tailscale logout as a last step in your ephemeral node deployment script to immediately remove it from your tailnetĪnother way is if you created an ephemeral device by running tailscaled with the -state=mem: flag. Run the tailscale logout command on an ephemeral device to remove it from your tailnet The next time your infrastructure spins up a new device, you should see it appear in your admin console as an ephemeral node! It will be able to connect to your network, and will be auto-removed shortly after going offline.Ĭan an ephemeral device remove itself from my tailnet?

See our guides on setting up common platforms: To create an ephemeral node, you’ll first need to generate an ephemeral auth key from the auth keys page of the admin console. You can identify ephemeral nodes in your admin console by looking for an “Ephemeral” badge underneath the device name. If you are deploying multiple instances of the same container, use a reusable auth key instead of baking the Tailscale node key into the container image to avoid duplicate devices.
#Ephemeral nodes rotation update#
To avoid updating every device’s netmap when an ephemeral device is added to the Tailscale network, consider using an ephemeral tagged auth key, and update ACLs to restrict what tagged devices can access.
