The Wire · Showcase
TEST INFRASTRUCTURE CLEANS UP CRUFT, KUBERNETES CORE FIXES CPU MANAGER TEST FAILURES
By RepoJournal · Filed · About Kubernetes
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
FAQ
- What changed 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.
- What should Kubernetes teams do about it?
- Review CPU Manager e2e test changes if you maintain node-level test suites • Sync theme_lock front matter in your localized documentation pages before dark mode lands • If you report CVEs, use the new unfixed CVE format in committee-security-response
- Which Kubernetes repositories shipped on June 1, 2026?
- kubernetes/test-infra, kubernetes/website, kubernetes/kubernetes, kubernetes/committee-security-response