Tailscale Kubernetes operator v1.68.1
This release adds support for proxies to accept routes from tailnet peers via the new acceptRoutes field, enables per-proxy image and pull policy configuration through ProxyClass, includes tailnet IP addresses and MagicDNS names in Connector Custom Resources status, and fixes Helm values to support standard repository key configuration.
A new release of the Tailscale Kubernetes operator is available. For guidance on installing and updating, see our installation instructions.
- New: Tailscale Kubernetes operator proxies can now be configured to accept routes advertised by tailnet peers using the new
proxyClass.spec.tailscale.acceptRoutesfield. To learn more, see our ProxyClass documentation. - New: Images and image pull policies can be configured for individual Tailscale Kubernetes operator proxies using ProxyClass.
- New: Connector Custom Resources status now includes the proxy's tailnet IP addresses and MagicDNS name.
- Fixed: Helm values file now allows configuring image repositories using a repository key, which is a standard and expected by some tools.
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.