The Wire · Showcase
AZURE CONFORMANCE TESTS PATCHED, DOCSY UPGRADE LIVE, INFRASTRUCTURE CLEANUP CONTINUES
By RepoJournal · Filed · About Kubernetes
Windows Azure conformance tests are now passing after removing a broken kubeconfig command, while the website team ships Docsy 0.7 and the infrastructure desk begins streamlining registry and monitoring tooling.
The test-infra desk shipped critical fixes for cloud-provider-azure Windows conformance tests [1] [2], removing a command that was blocking test execution. A separate fix skips the ServiceAccountIssuerDiscovery test in CAPZ workload clusters [3], a known environment limitation where Azure Blob Storage certificates lack the required CA bundle for TLS verification. The desk is also moving forward on resource standardization [4], working to align CPU and memory ceilings across clouds by adopting consistent 8-core 32GB instance sizes instead of current oversized deployments. Descheduler presubmits rotated for the 1.36 release [5], cycling test lanes from 1.35/1.34/1.33 to 1.36/1.35/1.34. On the website desk, Docsy upgraded to 0.7.2 [6], removing the sidebar navigation splitter and modernizing the site's component library. Release pages now display codenames [7], with themes stored as arrays to handle naming differences between SIG Release documentation and blog announcements. KubeCon India 2026 banner went live [8]. The k8s.io infrastructure desk dropped the storage migrator registry [10] following Slack discussion and updated GCP Terraform documentation across all modules [9]. Publishing-bot merged a go-git dependency bump to 5.19.1 [11]. Client-go fixed an informer store issue [12] [13] where the store was being set to noop and improved nil checks for store metrics.
Action items
- → Verify Azure Windows conformance tests pass in your pipeline kubernetes/test-infra [plan]
- → Review cloud instance sizing standardization proposal for your environment kubernetes/test-infra [monitor]
- → Update any internal documentation referencing storage-migrator registry kubernetes/k8s.io [plan]
- → Test client-go informer store fix in development builds kubernetes/client-go [monitor]
References
- [1] fix(cloud-provider-azure): remove broken command from conformance windows kubernetes/test-infra
- [2] Merge pull request #37055 from Liunardy/fix/conformance-windows-kubeconfig kubernetes/test-infra
- [3] Skip ServiceAccountIssuerDiscovery test in cloud-provider-azure-conformance-capz kubernetes/test-infra
- [4] enforce cpu/memory ceiling for prow jobs ↗ kubernetes/test-infra
- [5] descheduler: update presubmits for 1.36 release ↗ kubernetes/test-infra
- [6] Upgrade to Docsy 0.7 (no sidebar nav splitter) ↗ kubernetes/website
- [7] Add release codename in release pages ↗ kubernetes/website
- [8] Chore: add banner for KubeCon India 2026 ↗ kubernetes/website
- [9] docs: update gcp infra terraform docs ↗ kubernetes/k8s.io
- [10] drop storage migrator registry ↗ kubernetes/k8s.io
- [11] build(deps): bump github.com/go-git/go-git/v5 from 5.19.0 to 5.19.1 ↗ kubernetes/publishing-bot
- [12] Merge pull request #139143 from michaelasp/informerStoreFix kubernetes/client-go
- [13] Fix nil check for store metrics kubernetes/client-go
FAQ
- What changed in Kubernetes on May 19, 2026?
- Windows Azure conformance tests are now passing after removing a broken kubeconfig command, while the website team ships Docsy 0.7 and the infrastructure desk begins streamlining registry and monitoring tooling.
- What should Kubernetes teams do about it?
- Verify Azure Windows conformance tests pass in your pipeline • Review cloud instance sizing standardization proposal for your environment • Update any internal documentation referencing storage-migrator registry
- Which Kubernetes repositories shipped on May 19, 2026?
- kubernetes/test-infra, kubernetes/website, kubernetes/k8s.io, kubernetes/publishing-bot, kubernetes/client-go