LoginSign Up
← Back to all sparks
K

kOps

INFRA · APIS
Velocity3.8

Production-grade Kubernetes cluster provisioning and operations

kops.sigs.k8s.io ↗

kOps deletes gossip DNS and the protokube binary, and spends the room on Akamai.

kubernetescluster-lifecyclemulti-cloudbreaking-changessurface-reduction
◆Current state
kOps publishes alpha and beta tags to this feed rather than finals, and 1.37.0-beta.1 is the largest cut in its visible history. Gossip DNS is gone, along with the protokube binary that served it, Classic Load Balancer support for the API, and Kubernetes 1.31. In the same tag Akamai — renamed from Linode across the codebase — grows from SSH-key handling into a provider with its own network model, subnets, instance management and etcd block storage volumes.
◆Where it's heading
The deliberate narrowing this feed has shown since 1.36 has stopped being incremental. Removing gossip means every cluster now needs real DNS, which ends the configuration that let kOps stand up clusters without a hosted zone. The room that deletion frees is going two visible places: a genuinely new cloud provider in Akamai, and a smaller binary, via grpcnotrace, a forked text/template that lets the linker prune, and a minimal TOML writer replacing go-toml.
◆Prediction
Akamai moved from SSH keys to subnets, instances and etcd volumes inside a single tag, so it is the provider most likely to keep gaining tasks next. With a gossip migration guide already written, the remaining 1.37 work is the removal reaching users rather than more subtraction.

◆Recent moves

  1. 18d ago

    Gossip DNS and protokube removed; Akamai becomes a full provider

    ⚡ SPARK

    The narrowing this feed has shown since 1.36 arrives at its largest cut: gossip DNS, the protokube binary that served it, Classic Load Balancer support for the API and Kubernetes 1.31 all come out in one tag, with a migration guide alongside. The same tag builds Akamai into a provider with subnets, instance management and etcd volumes, so the subtraction and the expansion are funded together.

    View source ↗
  2. 2mo ago

    Azure attested node identity; AWS and GCE health check reconcile

    The reconciliation thread lands on both AWS target groups and GCE HTTP health checks in one tag, so drift in resources kOps already created now gets corrected. Azure switching to the IMDS attested metadata document for node identity is the security-relevant change, and Linode SSH key management is the first step of what becomes the Akamai provider one tag later.

    View source ↗
  3. 3mo ago

    Omitted authorization now defaults to RBAC instead of AlwaysAllow

    The default change is the item that matters: a cluster spec that omits authorization no longer gets AlwaysAllow. It reads as an early instance of the same instinct that later removes gossip and the Classic Load Balancer — trading a permissive legacy path for a narrower supported one. Addon apply failures also surface through a readiness probe rather than staying silent.

    View source ↗
  4. 3mo ago

    Amazon Linux 2 support removed; warm pools take user-defined images

    Removing Amazon Linux 2 and updating the distribution matrix around it is the first visible platform subtraction in this window, and it forces migration for anyone still on it. Warm pool instances pulling user-defined images is the useful addition for teams managing their own AMIs.

    View source ↗