LoginSign Up
← Back to all sparks
T

Tailscale

INFRA · APIS
Velocity6.3

Tailscale is turning the tailnet itself into something a script provisions and pages through.

networkingzero-trustkubernetesmulti-tenancyapi-platform
◆Current state
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
◆Where it's heading
Tailscale has spent this period on two different customers at once. The operator work serves platform teams running Tailscale inside Kubernetes, where the gaps being closed are reconciliation loops, stale DNS ConfigMaps and cert-renewal backoff. The tailnet API work serves a different shape entirely: organizations holding enough tailnets that a hundred is a page boundary, which only happens when tailnets are allocated per customer or per environment rather than per company. The second thread is the one that changes what Tailscale is for.
◆Prediction
Pagination on list implies the creation API is being used at volume, so expect the alpha to gain the management operations a fleet needs — policy templating or bulk configuration across tailnets. The client release line looks settled on 1.102.x maintenance in the near term.

◆Recent moves

  1. 1d ago

    Tailnet list API pagination

    The list tailnets endpoint now paginates, capping default responses at 100 with limit and cursor parameters. It is a behaviour change callers must handle, and it is also a tell: pagination on this endpoint only matters once organizations are running tailnets in the hundreds, which is exactly what the creation API three weeks earlier made possible.

  2. 8d ago

    Operator adds in-cluster PeerRelays and workload identity federation

    The Kubernetes operator gains in-cluster PeerRelays via custom resource, workload identity federation on the Tailnet resource, 4via6 in dual-stack egress and IPv6 in Egress ProxyGroups, plus a long run of reconciliation fixes. Workload identity federation is the piece that matters for teams trying to stop managing auth keys in-cluster.

  3. 12d ago

    Container image v1.102.2: library updates only

    A container image release carrying nothing but library updates, bundled with a tsrecorder fix for empty recording placeholders. Housekeeping on the packaging line.

  4. 15d ago

    v1.102.2 fixes a Funnel incoming-connection regression

    A single-issue patch resolving a regression that broke incoming Funnel connections. Restores prior behaviour rather than adding any.

  5. 16d ago

    v1.102.1 adds Services CLI and constant-time node churn

    A substantial client release adding Serve byte-count metrics for Tailscale Services, and CLI commands for reading node preferences and identity. Observability and introspection for the Services surface Tailscale has been building out.

  6. 21d ago

    Tailnet creation API

    ⚡ SPARK

    The release the rest of this window orbits: tailnets became something an API creates and deletes rather than something an organization signs up for. The pagination change three weeks later is the first visible consequence.