# IPv6 support for the Tailscale Kubernetes Operator

Last validated Jun 5, 2026

The following summarizes IPv6 support for each proxy mode.

## Singleton proxy

| Feature          | IPv6 support | Cluster requirement                                                                             |
| ---------------- | ------------ | ----------------------------------------------------------------------------------------------- |
| Ingress          | Supported    | Dual-stack cluster required to expose Kubernetes `Service`s over both IPv4 and IPv6 ClusterIPs. |
| Egress           | Supported    | None                                                                                            |
| API Server Proxy | Supported    | None                                                                                            |

## ProxyGroup

| Feature          | IPv6 support  | Cluster requirement                                                                                |
| ---------------- | ------------- | -------------------------------------------------------------------------------------------------- |
| Ingress          | Supported     | Dual-stack cluster required to expose Kubernetes `Service`s over both IPv4 and IPv6 ClusterIPs.    |
| Egress           | Not supported | IPv4 only. IPv6 tailnet targets are not supported. The cluster must assign IPv4 addresses to pods. |
| API Server Proxy | Supported     | None                                                                                               |

> **Note:**
>
> Pods cannot reach tailnet devices by raw Tailscale IPv6 address (`fd7a:...` / [4via6][kb-4via6]). Use MagicDNS names or IPv4 addresses instead.

[kb-4via6]: /docs/features/subnet-routers/4via6-subnets