Tailscale 1.94.2
Please refer to the changelog available at https://tailscale.com/changelog
Please refer to the changelog available at https://tailscale.com/changelog
- Changed: Use workload identity federation ( generally available ) to authenticate Tailscale API requests with federated OIDC workload identities from third-party providers.
- Changed: Use Tailscale Peer Relays to set up self-hosted high-throughput relay servers when direct connections aren't possible ( generally available ).
- New: Use Aperture by Tailscale to secure and monitor LLM sessions and AI agents ( alpha ).
A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions . Fixed: Configuring a single invalid Tailscale FQDN for an egress will no longer cause the egress to crash. It will instead log the error and continuing serving traffic.
All Platforms Fixed: Memory leak caused by high network map response rates is resolved.
A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions . New: The Egress proxy can now send traffic to Tailscale service VIPs.
- New: Tailscale network flow logs and configuration audit logs can be streamed to Google Cloud Storage (GCS).