RepoJournal
Kubernetes

@kubernetes

Container orchestration - what platform teams ship on

Keep up with Kubernetes in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

KARPENTER LANDS IN KOPS, KUBE-PROXY CUTS CADVISOR DEPENDENCY

By RepoJournal · Filed · About Kubernetes

Kops now ships native Karpenter EC2NodeClass and NodePool support while kube-proxy eliminates its cadvisor dependency by reading CPU topology directly from cpuset.

Kops merged full managed Karpenter integration [1], giving operators declarative EC2NodeClass and NodePool configuration without leaving the kops cluster spec. This lands alongside command-line slice expansion [2], which now allows paths like `cluster.spec.addons[0].manifest` to create missing array elements on the fly, unblocking Gateway API CRD installation via the addon system. Across the cluster, kube-proxy shed its cadvisor dependency [3][4] in favor of cpuset.NumCPU() from k8s.io/utils, a cleaner read of actual node topology that matters for conntrack sizing under static CPU policies. The scheduler gained resourceVersion awareness in Pod status patches [5], tightening consistency guarantees. Test infrastructure is marching forward: CAPZ release-1.25 branch replaces EOL release-1.23 in periodic jobs [6], and the 5k-node scale job got realigned with non-experimental baselines [7]. On the warning front, kubelet now only surfaces missing pull secret alerts when image pulls actually fail [8], cutting noise for clusters that don't rely on private registries.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Add managed Karpenter EC2NodeClass and NodePool ↗ kubernetes/kops
  2. [2] Allow setting missing slice elements from the command line ↗ kubernetes/kops
  3. [3] kube-proxy: detect host CPU count via cpuset.NumCPU instead of cadvisor kubernetes/kubernetes
  4. [4] kube-proxy: detect host CPU count via cpuset.NumCPU instead of cadvisor ↗ kubernetes/kubernetes
  5. [5] scheduler: Add resourceVersion to Pod status patch ↗ kubernetes/kubernetes
  6. [6] Add CAPZ release v1.25 tests ↗ kubernetes/test-infra
  7. [7] Merge pull request #37339 from Jefftree/drop-etcd-version-pull-5k kubernetes/test-infra
  8. [8] Only warn about missing pull secrets if image pull fails ↗ kubernetes/kubernetes

Quick answers

What shipped in Kubernetes on June 27, 2026?
Kops now ships native Karpenter EC2NodeClass and NodePool support while kube-proxy eliminates its cadvisor dependency by reading CPU topology directly from cpuset. In total, 54 commits and 21 pull requests landed.
Who contributed to Kubernetes on June 27, 2026?
5 developers shipped this update, including hakman, dims, nojnhuh, mboersma, and Jamstah.
What were the notable Kubernetes updates?
Add managed Karpenter EC2NodeClass and NodePool, Allow setting missing slice elements from the command line, and kube-proxy: detect host CPU count via cpuset.NumCPU instead of cadvisor.

More from @kubernetes

Daily updates, in your inbox

Follow Kubernetes

Keep up with Kubernetes in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.