RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

The Wire · Showcase

KOPS REWRITES IMAGE PIPELINE, TEST-INFRA KILLS ZOMBIE JOBS

By RepoJournal · Filed · About Kubernetes

Kubernetes is gutting seven-year-old containerized mounter code and streaming images directly into containerd—a two-part nodeup overhaul that cuts disk I/O and hardens image verification.

The kops team shipped two foundational changes that reshape how nodes boot [1][2]. First, they're dropping the mounter.tar payload and Archive task—deprecated infrastructure frozen since January 2017 that only NFS in-tree volumes ever used [1]. Users running that setup need to migrate to kubernetes-csi/csi-driver-nfs before upgrading. Second, they're replacing the three-step download-ungzip-reference flow with a streaming pipeline that hashes on arrival and pipes directly to ctr import, eliminating intermediate disk materialization and preventing corrupted bytes from reaching containerd [2]. This is the kind of plumbing work that makes everything downstream faster and safer. Over on test-infra, maintainers are finally burying jobs that have been failing for years [3]. The ci-kubernetes-soak jobs for k8s 1.12-1.15 reference GCS channels that 404 every single run—stable1 through stable3 cover what's actually supported. Meanwhile, sig-node fixed a kubelet failure: NodeSwap graduated to GA with LockToDefault:true in v1.34, so explicitly passing --feature-gates=NodeSwap=true now breaks startup [4]. The website team continues steady documentation sync across Chinese localizations with no blocking issues.

Action items

References

  1. [1] nodeup: drop containerized mounter and Archive task ↗ kubernetes/kops
  2. [2] nodeup: stream verified image bytes into ctr import ↗ kubernetes/kops
  3. [3] config: retire EOL GCE soak jobs for k8s 1.12-1.15 kubernetes/test-infra
  4. [4] jobs/sig-node: remove NodeSwap=true feature gate from node-swap-ubuntu-serial kubernetes/test-infra

FAQ

What changed in Kubernetes on May 7, 2026?
Kubernetes is gutting seven-year-old containerized mounter code and streaming images directly into containerd—a two-part nodeup overhaul that cuts disk I/O and hardens image verification.
What should Kubernetes teams do about it?
If running in-tree NFS PVs, plan migration to kubernetes-csi/csi-driver-nfs before next kops upgrade • Remove --feature-gates=NodeSwap=true from any node-swap-ubuntu-serial test configurations • Monitor kops nodeup deployments for streaming image verification behavior in staging
Which Kubernetes repositories shipped on May 7, 2026?
kubernetes/kops, kubernetes/test-infra

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • 14 famous open source orgs
  • One wire per day
  • Public, generic
  • Read on the web, when you remember

Your wire

  • Up to 1,500 of your repos - orgs, deps, vendors
  • Morning and evening briefs
  • Action items routed to your team
  • Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.