LoginSign Up
← Back to all sparks
Kubernetes logo

Kubernetes

DEVOPSINFRA · APIS
Velocity5.0

Container orchestration

kubernetes.io ↗

Kubernetes moves conformance from the cluster to the workloads running on it.

conformanceworkload standardscgroup v2resource managementupgrades
◆Current state
Kubernetes is between releases, and its feed is v1.37 feature deep-dives, migration guidance and ecosystem tooling. The cgroup v2 FAQ, node swap benchmarks and Memory QoS beta all push operators toward newer node defaults. The newest item is a governance move: a Workload Conformance Working Group chartered to test applications, not clusters.
◆Where it's heading
The project keeps codifying operational knowledge that operators used to hold in their heads: unused-PVC conditions, pod-level resource managers, and now a planned spec for how workloads behave during drains, upgrades and resource use. Conformance is widening from Certified Kubernetes to AI Conformance to workloads, each with objective, binary tests.
◆Prediction
Expect the working group to publish a first requirements draft for community input, with stable tests targeted two to three release cycles out. In the meantime, the blog will likely keep shipping v1.37 graduation write-ups and migration FAQs.

◆Recent moves

  1. 2d ago

    Announcing the Workload Conformance Working Group

    A new Workload Conformance Working Group will write a per-minor-version spec for how applications behave on Kubernetes, covering disruption tolerance, privileges, resource use and API usage, plus upstream tests to check it. It extends the conformance idea from clusters to workloads and gives operators a shared baseline instead of repeating hand audits before every upgrade. Nothing is specified yet; the target is a stable first spec in two to three releases.

    View source ↗
  2. 14d ago

    Why Is My Kubernetes Job Still Pending? Tracing Kueue Admission with Headlamp

    A walkthrough of the 0.1.0-alpha Kueue plugin for Headlamp, which shows read-only Workload, queue, ResourceFlavor and Cohort views so a stuck Job's admission can be traced in the UI instead of across YAML dumps. It extends the recent run of operator guidance, this time for batch and AI jobs queued behind quota.

    View source ↗
  3. 22d ago

    The Shift to cgroup v2 in Kubernetes: What You Need to Know

    A migration FAQ for cgroup v2, prompted by v1.35 making the kubelet fail on cgroup v1 nodes by default and kubeadm preflight now erroring on them. It is the prerequisite for the release's memory features, which assume the unified hierarchy, and it signals that full v1 removal is coming.

    View source ↗
  4. 23d ago

    Scaling Kubernetes Workloads with Node Swap

    A benchmark write-up on backing node swap with NVMe SSDs to page out idle memory and fit more pods per node, framed around agentic AI workloads that sit resident between prompts. It is guidance on an existing GA feature, but it ties the v1.37 memory work to a concrete density argument.

    View source ↗
  5. 1mo ago

    Spotlight on SIG Apps

    A community profile of SIG Apps, the group behind Deployments, StatefulSets and Jobs. No product change.

    View source ↗
  6. 1mo ago

    Kubernetes v1.37: Tracking When a PersistentVolumeClaim Was Last Used (Beta)

    PVCs now carry an Unused condition by default, so operators can find orphaned storage without custom tooling. It is part of v1.37's push to make storage state legible.

    View source ↗