Tailscale Kubernetes operator v1.80.0
New release featuring optional ServiceMonitor labeling for proxy metrics, dynamic tailscaled configuration reloading for proxies, improved TLS certificate requests with DNS names in CSR, and fixed failover handling for egress ProxyGroup replicas to eliminate downtime during restarts.
A new release of the Tailscale Kubernetes operator is available. For guidance on installing and updating, see installation instructions.
- New: The optional
ServiceMonitorcreated for the proxy metrics endpoints can be labeled with user-specified labels. - New: Proxies created for the Kubernetes Operator dynamically reload the tailscaled configuration when it has changed. Changes such as a hostname might mean slightly slower change propagation (up to a minute), but less downtime.
- Changed: TLS certificate requests from Let's Encrypt include the device's DNS name in the CSR's SAN extension and set the
Common Namefield. - Fixed: Improved failover for egress
ProxyGroupreplicas. Replica restarts no longer cause downtime for cluster workloads that access tailnet targets using egressProxyGroup.
Source: original entry ↗
More from Tailscale
Follow Tailscale to get its new changes in your feed and email digest.
Tailscale v1.104.1 — Performance and Features Release
Tailscale v1.104.1 delivers significant performance improvements including reduced WireGuard memory usage, client-side netmap caching for offline resilience, and enhanced features like device pinning, improved Taildrop support, and platform-specific fixes across all supported devices.
Declarative node sharing
Tailnet admins can now use policy to securely share resources between trusted tailnets in a declarative way, enabling controlled cross-tailnet access.
Linux client reconnection stability fix
Fixed an issue where the Linux client would stop tailscaled when falling behind on status updates. The client now reconnects instead of exiting, and only terminates if it cannot reconnect within one minute.