RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

  1. Wed 27 may
  2. Thu 28 may
  3. Fri 29 may
  4. Sat 30 may
  5. Sun 31 may
  6. Mon 1 jun
  7. Mon 8 jun
  8. Tue 9 jun
  9. Wed 10 jun
  10. Thu 11 jun
  11. Fri 12 jun
  12. Sat 13 jun
  13. Sun 14 jun
  14. Mon 15 jun
  15. Tue 16 jun
  16. Wed 17 jun
  17. Thu 18 jun
  18. Fri 19 jun
  19. Sat 27 jun
  20. Sun 28 jun
  21. Mon 29 jun
  22. Tue 30 jun
  23. Wed 1 jul
  24. Thu 2 jul
  25. Fri 3 jul
  26. Sat 4 jul
  27. Sun 5 jul
  28. Mon 6 jul
  29. Tue 7 jul
  30. Today 8 jul

The Wire · Showcase

STRUCTURED MERGE REGRESSION FIXED ACROSS CONTROL PLANE

By RepoJournal · Filed · About Kubernetes

Kubernetes rolled back a breaking change in server-side apply that corrupted nullable container patches, with the fix propagating across kube-scheduler, endpoints, and resource allocation components within hours.

The core issue was a regression introduced in structured-merge-diff that broke server-side apply for nullable container types [1]. Kubernetes bumped SMD to v6.4.2 to revert the problematic change, and that dependency update is now landing across multiple control plane repositories [2] [3] [4] [5] [6] [7]. In parallel, audit logging got a critical fix for CBOR apply patches that were failing serialization due to binary data in request objects [8]. The logging layer also tightened up nil pointer handling in structured logs, distinguishing between typed nil pointers and empty references [9]. Static pod validation improved with new warnings when kubelet encounters invalid priority and priorityClassName combinations . SVM has been promoted to general availability [10], and deprecated pod log metrics have been cleaned up [11].

Action items

References

  1. [1] Bump SMD to v6.4.2 to revert #306 to fix regression in SSA for nullable container types ↗ kubernetes/kubernetes
  2. [2] Merge pull request #140294 from jpbetz/revert-smd-306 kubernetes/endpointslice
  3. [3] Bump sigs.k8s.io/structured-merge-diff/v6 to v6.4.2 kubernetes/endpointslice
  4. [4] Merge pull request #140294 from jpbetz/revert-smd-306 kubernetes/kube-scheduler
  5. [5] Bump sigs.k8s.io/structured-merge-diff/v6 to v6.4.2 kubernetes/kube-scheduler
  6. [6] Merge pull request #140294 from jpbetz/revert-smd-306 kubernetes/dynamic-resource-allocation
  7. [7] Bump sigs.k8s.io/structured-merge-diff/v6 to v6.4.2 kubernetes/dynamic-resource-allocation
  8. [8] Fix CBOR apply patch request audit ↗ kubernetes/kubernetes
  9. [9] Fix KObjSlice logging nil pointer entries as empty string ↗ kubernetes/klog
  10. [10] Promote SVM to GA ↗ kubernetes/kubernetes
  11. [11] Merge pull request #140038 from tico88612/cleanup/pod-logs-deprecated-metrics kubernetes/kubernetes

FAQ

What changed in Kubernetes on July 8, 2026?
Kubernetes rolled back a breaking change in server-side apply that corrupted nullable container patches, with the fix propagating across kube-scheduler, endpoints, and resource allocation components within hours.
What should Kubernetes teams do about it?
Pin structured-merge-diff to v6.4.2 minimum in your control plane builds • Verify SSA patches for nullable containers work in your test environment • Update klog dependency to pick up nil pointer logging fix
Which Kubernetes repositories shipped on July 8, 2026?
kubernetes/kubernetes, kubernetes/endpointslice, kubernetes/kube-scheduler, kubernetes/dynamic-resource-allocation, kubernetes/klog

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.