Who contributed to Kubernetes on June 1, 2026?

5 developers shipped this update, including windsonsea, Eundms, Caesarsage, dims, and tabbysable.

What were the notable Kubernetes updates?

Merge pull request #37147 from adrianmoisey/remove-debug-and-cp, Merge pull request #37150 from Liunardy/oot-cred-provider-non-ci-template, and fix(cloud-provider-azure): use OOT credential provider template for v1.30 and v1.31.

@kubernetes

Container orchestration - what platform teams ship on

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

TEST INFRASTRUCTURE CLEANS UP CRUFT, KUBERNETES CORE FIXES CPU MANAGER TEST FAILURES

By RepoJournal · Filed 06:01 UTC on June 1, 2026 · About Kubernetes

5 people shipped this

windsonsea @windsonsea 1 cited

Eundms @Eundms 1 cited

Caesarsage @Caesarsage 1 cited

dims @dims 1 cited

tabbysable @tabbysable 1 cited

The test-infra team removed debug code bloat overnight while the core Kubernetes project patched failing e2e tests that were crashing under v1.37's locked CPU quota settings.

Test-infra merged cleanup work [1] stripping unnecessary debug statements and copy operations that were accumulating in the codebase. On the cloud provider front, the Azure credential provider got updated to use out-of-tree templates for v1.30 and v1.31 [2][3], a pattern shift that decouples provider-specific auth from core test infrastructure. In parallel, the node-readiness-controller gained a presubmit job [4] to catch regressions earlier in the PR cycle. The bigger story came from kubernetes/kubernetes where CPU Manager e2e tests started failing because DisableCPUQuotaWithExclusiveCPUs was locked to true in v1.37, causing the test block that sets it to false to crash the kubelet [9][10]. That's been fixed by skipping the now-invalid test case while keeping coverage of the enabled behavior. On the documentation side, the website desk synced localization updates across Chinese and Korean variants [5][6], and added theme_lock front matter to concept pages [7][8] in preparation for the upcoming dark mode switcher. The security committee also published guidance on correctly formatting unfixed CVEs in public records [11][12], clarifying how to express vulnerabilities that won't be patched.

Action items

→ Review CPU Manager e2e test changes if you maintain node-level test suites kubernetes/kubernetes [plan]
→ Sync theme_lock front matter in your localized documentation pages before dark mode lands kubernetes/website [plan]
→ If you report CVEs, use the new unfixed CVE format in committee-security-response kubernetes/committee-security-response [monitor]

References

[1] Merge pull request #37147 from adrianmoisey/remove-debug-and-cp kubernetes/test-infra
[2] Merge pull request #37150 from Liunardy/oot-cred-provider-non-ci-template kubernetes/test-infra
[3] fix(cloud-provider-azure): use OOT credential provider template for v1.30 and v1.31 kubernetes/test-infra
[4] Merge pull request #37035 from vitorfloriano/prow-node-readiness-controller-presub-test kubernetes/test-infra
[5] [zh] Sync hugo-shortcodes/index.md ↗ kubernetes/website
[6] [ko] Update content/ko/docs/concepts/scheduling-eviction/_index.md ↗ kubernetes/website
[7] Merge pull request #55964 from Caesarsage/theme-lock-front-matter kubernetes/website
[8] Add theme_lock front matter to concepts overview pages ↗ kubernetes/website
[9] e2e: node: cpumanager: skip DisableCPUQuotaWithExclusiveCPUs=false tests ↗ kubernetes/kubernetes
[10] Merge pull request #139392 from dims/skip-cpumanager-cfsquota-disabled kubernetes/kubernetes
[11] Include directions for correctly formatting unfixed CVEs ↗ kubernetes/committee-security-response
[12] Merge pull request #226 from tabbysable/unfixed-cves kubernetes/committee-security-response

Quick answers

What shipped in Kubernetes on June 1, 2026?: The test-infra team removed debug code bloat overnight while the core Kubernetes project patched failing e2e tests that were crashing under v1.37's locked CPU quota settings. In total, 11 commits and 10 pull requests landed.
Who contributed to Kubernetes on June 1, 2026?: 5 developers shipped this update, including windsonsea, Eundms, Caesarsage, dims, and tabbysable.
What were the notable Kubernetes updates?: Merge pull request #37147 from adrianmoisey/remove-debug-and-cp, Merge pull request #37150 from Liunardy/oot-cred-provider-non-ci-template, and fix(cloud-provider-azure): use OOT credential provider template for v1.30 and v1.31.

SCHEDULER GAINS PREQUEUING FILTER, KUBELET USER NAMESPACES MOVE TO BETA

Kubernetes tackles the pod requeue bottleneck that's been choking large clusters, while user namespacing ships closer to production.

go 19 shipped 1-min read

@kubernetes 1 day ago

CLUSTER-AUTOSCALER PATCHES HIT ALL RELEASE BRANCHES AS DRA AND VOLUMEMOUNT BIND OPTIONS LAND

Cluster-autoscaler shipped four patch releases across versions 1.33 through 1.36 fixing ProvisioningRequest condition application and Scaleway node detection, while Kubernetes core merged DRA node operations and volumeMount bind mount options.

go 89 shipped 1-min read

@kubernetes 2 days ago

DRA GETS SMARTER RESOURCE ACCOUNTING, CLUSTER-AUTOSCALER ROLLS OUT FOUR PATCHES

Dynamic Resource Allocation fixed device accounting across its resource pool controller while cluster-autoscaler shipped maintenance releases across four versions.

go 52 shipped 1-min read

@kubernetes 3 days ago

DRA GRADUATES TO STABLE, KUBELET METRICS BYPASS CADVISOR, NAMESPACE LIFECYCLE UNBLOCKED

Three critical production fixes ship across core scheduler, metrics, and admission layers while DRA resource tracking stabilizes after surfacing a crash bug in the informer.

go 129 shipped 1-min read

Elsewhere on the wire

AI Agents about 9 hours ago

CLAUDE OPUS 5 LANDS ACROSS THE STACK

The newest Anthropic model is now live in langchain, Cline, and llama-index, with native support for extended reasoning and 1M context windows.

ai-agents 28 shipped 1-min read

Local LLMs about 9 hours ago

OLLAMA LANDS LAGUNA SUPPORT AND CRUSHES MEMORY LEAKS WHILE SGLANG HITS V0.5.16 WITH CONFIDENCE-DRIVEN SPECULATIVE DECODING

Ollama shipped three critical performance and reliability fixes for Metal residency and concurrent access patterns, while SGL-Lang released 0.5.16 with a new speculative algorithm hitting 383.7 tok/s on DeepSeek-V4.