Tailscale Kubernetes Operator v1.96.5
New features include authkey refresh for Ingress/Egress ProxyGroup pods, multiple tailnet access via new Tailnet custom resource, and namespace-level ProxyGroup creation controls via ProxyGroupPolicy. Removed TS_EXPERIMENTAL_KUBE_API_EVENTS variable and fixed TS_LOCAL_ADDR_PORT handling for IPv6 addresses.
A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.
- New: Ingress and Egress ProxyGroup pods are able to request a new authkey when required.
- New: Multiple tailnet access can be enabled with the use of the new Tailnet custom resource.
- New: ProxyGroup creation controls can be managed by namespace with the new ProxyGroupPolicy custom resource.
- Changed: The environment variable
TS_EXPERIMENTAL_KUBE_API_EVENTSis removed. This can instead be set via Tailscale ACLs. - Fixed: The environment variable
TS_LOCAL_ADDR_PORTno longer fails when it is populated with an IPv6 address without brackets.
Source: original entry ↗
More from Tailscale
Follow Tailscale to get its new changes in your feed and email digest.
Self-serve identity provider changes GA
Owner role users can now switch their tailnet's identity provider from the admin console for supported providers, which is now generally available.
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.
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.