Who contributed to Kubernetes on July 4, 2026?

4 developers shipped this update, including nirs, mimowo, antekjb, and hakuna-matatah.

What were the notable Kubernetes updates?

drivers: Start vm drivers in parallel, kvm: Fix empty IP when starting profiles in parallel, and Kueue: drop CI job for 1.33.

Jul 4, 2026

$ the-wire · showcase

MINIKUBE PARALLELIZES VM STARTUP, KUBERNETES 1.33 REACHES END OF LIFE

By RepoJournal · Filed 06:01 UTC on July 4, 2026 · About Kubernetes · Composed from the cited sources · methodology

4 people shipped this

nirs @nirs 1 cited

mimowo @mimowo 1 cited

antekjb @antekjb 1 cited

hakuna-matatah @hakuna-matatah 1 cited

Minikube eliminates serialization bottleneck for concurrent cluster creation, cutting multi-cluster setup times by 25 seconds per profile.

The minikube team shipped a fix [1] that removes the single driver lock preventing parallel VM startup for safe drivers like KVM2. Previously, even independent clusters using the same driver would serialize start commands due to VirtualBox's inability to handle concurrent calls, a constraint that doesn't apply to modern drivers where each profile gets its own isolated VM or container. This change unblocks tools like RamenDR that spin up multiple clusters in parallel. Supporting this fix are patches addressing the KVM driver's IP address handling under parallel stress [2], where GetIP() now correctly returns cached addresses instead of re-querying libvirt on every call. Meanwhile, Kubernetes 1.33 has hit end-of-life [3], triggering cleanup across the test infrastructure. The scheduler ecosystem continues optimization work with WAP logic decoupled from the scheduler struct [4] and a new HPASelectoreStore designed to reduce Read/Write lock contention [5], improving HPA performance under load.

Action items

→ Update minikube if you run parallel cluster deployments to unblock faster development iteration kubernetes/minikube [plan]
→ Drop Kubernetes 1.33 from any internal test matrices and CI pipelines kubernetes/test-infra [plan]
→ Monitor scheduler performance metrics post-WAP decoupling for any regressions in your environment kubernetes/kubernetes [monitor]

References

[1] drivers: Start vm drivers in parallel ↗ kubernetes/minikube
[2] kvm: Fix empty IP when starting profiles in parallel ↗ kubernetes/minikube
[3] Kueue: drop CI job for 1.33 ↗ kubernetes/test-infra
[4] Decouple WAP logic from scheduler struct ↗ kubernetes/kubernetes
[5] Introduce new HPASelectoreStore which is optimized for Read/Write lock contention and helps improve performance. ↗ kubernetes/kubernetes