The Wire · Showcase
KUBERNETES 1.37 CLEANS HOUSE AS KARPENTER V1 ADOPTION ACCELERATES
By RepoJournal · Filed · About Kubernetes
Kubernetes is purging three deprecated API versions ahead of 1.37 release while kOps moves fast to align with Karpenter v1 semantics and drops support for obsolete master node labels.
The core Kubernetes repository merged cleanup work removing v1alpha1 clustertrustbundles, v1beta1 IPAddress/ServiceCIDR, and v1beta1 volumeattributesclasses [1], all deprecated in 1.34 and replaced by newer versions. This is the expected cadence: APIs get three releases before removal. In parallel, kOps is executing a coordinated upgrade to Karpenter v1.13.0 [2] with three foundational changes happening simultaneously. First, kOps now matches Karpenter's v1 label scheme by replacing the deprecated karpenter.sh/provisioner-name with karpenter.sh/nodepool [3]. Second, it's removing affinity rules keyed on the obsolete node-role.kubernetes.io/master label [4], which hasn't existed since Kubernetes 1.24/1.25. Third, kOps is adopting kustomize-based generation for the Karpenter addon manifest [5], eliminating hand-applied customizations that broke on every version bump. On the test-infra side, DRA (Dynamic Resource Allocation) is getting comprehensive E2E node presubmit coverage [6] to catch regressions before they land in kubernetes/kubernetes. The cacher subsystem refactored its key handling [7] to support sharing utilities across components, and the workload API gained mutability for minCount fields [8], improving flexibility for batch scheduling scenarios.
Action items
- → Upgrade kOps clusters to Karpenter v1.13.0 and verify nodepool labels are applied correctly kubernetes/kops [plan]
- → Audit any custom affinity rules targeting node-role.kubernetes.io/master and update to control-plane before 1.37 kubernetes/kops [plan]
- → Review deprecation timeline for v1alpha1 clustertrustbundles and v1beta1 IPAddress/ServiceCIDR in your manifests kubernetes/kubernetes [monitor]
References
- [1] Clean up expired APIs for 1.37 ↗ kubernetes/kubernetes
- [2] Upgrade Karpenter to v1.13.0 ↗ kubernetes/kops
- [3] Replace deprecated karpenter.sh/provisioner-name with karpenter.sh/nodepool kubernetes/kops
- [4] Remove obsolete node-role.kubernetes.io/master affinity term kubernetes/kops
- [5] Generate karpenter addon manifest with kustomize kubernetes/kops
- [6] DRA: generate E2E node presubmits for test-infra ↗ kubernetes/test-infra
- [7] cacher: move hasPathPrefix helper to new key subpackage ↗ kubernetes/kubernetes
- [8] Make minCount mutable in Workload and PodGroup APIs ↗ kubernetes/kubernetes
FAQ
- What changed in Kubernetes on June 18, 2026?
- Kubernetes is purging three deprecated API versions ahead of 1.37 release while kOps moves fast to align with Karpenter v1 semantics and drops support for obsolete master node labels.
- What should Kubernetes teams do about it?
- Upgrade kOps clusters to Karpenter v1.13.0 and verify nodepool labels are applied correctly • Audit any custom affinity rules targeting node-role.kubernetes.io/master and update to control-plane before 1.37 • Review deprecation timeline for v1alpha1 clustertrustbundles and v1beta1 IPAddress/ServiceCIDR in your manifests
- Which Kubernetes repositories shipped on June 18, 2026?
- kubernetes/kubernetes, kubernetes/kops, kubernetes/test-infra