Tailscale Kubernetes operator v1.88.2
ProxyClass now supports priorityClassName for pods, Connector resources allow multiple replicas for high availability, and fixes for DNSConfig with egress ProxyGroups and multi-cluster ingress certificate errors.
A new release of the Tailscale Kubernetes operator is available. For guidance on installing and updating, refer to our installation instructions.
- New: ProxyClass resources supports setting a
priorityClassNamefor created Pods. - New: Connector resources can specify multiple replicas for highly available subnet routers, app connectors, and exit nodes.
- Fixed: DNSConfig resource works as expected for egress ProxyGroups.
- Fixed: Multi-cluster ingress devices no longer display an erroneous "Invalid certificate" message in the Machines page of the admin console.
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.