Improvement1.92.3
Tailscale Kubernetes Operator v1.92.3
This release adds workload identity federation support for tailnet authentication and HTTP-to-HTTPS redirect annotations for Ingress resources. It also improves operator defaults, enables multi-replica Recorder deployments, fixes ArgoCD compatibility, and resolves issues with managed Ingress reconciliation and ProxyGroup-backed Ingress deletion.
A new release of the Tailscale Kubernetes Operator is available. For guidance on installing and updating, refer to our installation instructions.
- New: The operator supports workload identity federation for authenticating to a tailnet using provider-native identity tokens.
- New:
tailscale.com/http-redirectannotation can be applied to Ingress resources for enabling HTTP to HTTPS redirects. - Changed: The operator defaults to using the stable image for nameservers deployed using the
DNSConfigresource. - Changed: Recorder resources can specify a replica count for highly available deployments. Using multiple replicas requires using an S3 storage backend.
- Fixed: ArgoCD compatibility is improved. You can use both boolean and string values when setting the
apiServerProxyConfig.modeandapiServerProxyConfig.allowImpersonationvalues. - Fixed: The operator correctly reconciles managed Ingresses sharing the same namespace as other unmanaged Ingresses.
- Fixed:
ProxyGroupbacked ingresses no longer get stuck during deletion if they use a Tailscale Service that had been deleted.
kubernetesoperatoridentityingressdns
Source: original entry ↗