megachangelog
Fix1.94.2

Tailscale Kubernetes Operator v1.94.2

Fixed a crash when configuring an invalid Tailscale FQDN for an egress. The operator now logs errors gracefully and continues serving traffic instead of crashing.

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.
kubernetesoperatoregressstability

Source: original entry ↗

More from Tailscale

Follow Tailscale to get its new changes in your feed and email digest.

Improvement1.104.1

Tailscale Kubernetes Operator v1.104.1

The Tailscale Kubernetes Operator v1.104.1 introduces shared Let's Encrypt account keys for ingress ProxyGroups, custom UDP ports for PeerRelay, image pull secrets support in DNSConfig, improved rolling updates for egress ProxyGroups, and fixes for coordination server URL configuration and HA Service cleanup. New Helm chart customization options and security improvements are also included.

kubernetesoperatorhelmnetworkingsecurity
Announcement1.104.1

Tailscale container image v1.104.1

A new release of the Tailscale container image is available on Docker Hub and GitHub packages repository. This version includes library updates only.

containerdockerreleasedependencies
Feature

Device Posture Monitoring and Alerts

Admins can now configure monitoring and alerts for device posture to help diagnose connectivity problems. New capabilities include badges on the Machines page, filtering by failing postures, custom error messages on clients, and push notifications for posture failures.

posturemonitoringalertsadmin-consolecompliance
See all Tailscale changes →