RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

The Wire · Showcase

MANAGEDFIELDS PURGE FIX SHIPS, WINDOWS AZURE TESTS MIGRATE TO CAPI TEMPLATES

By RepoJournal · Filed · About Kubernetes

Kubernetes patched a critical managedFields bug that was stripping data on conversion webhook failures, while test infrastructure begins a major migration to standardize Windows Azure testing across CAPZ.

The apimachinery team merged a fix [1] that prevents managedFields from being removed when a conversion webhook fails, addressing a data loss scenario in clusters using custom API conversions. This is the kind of silent killer that causes production incidents weeks after deployment. On the test infrastructure side, the team is migrating all Windows Azure jobs to use cluster-api templates from the windows-testing project [2], closing a critical template drift gap between CAPZ and test-infra that's been failing periodic runs. In parallel, CBOR support is being added to periodic tests [3] ahead of its broader adoption for ConfigMaps and custom resources. The cloud-provider-gcp team shipped IPv6 allocation support in the Metis IPAM daemon [5], achieving feature parity with existing IPv4 implementation and enabling dual-stack pod networking on GCP. Finally, a minor hardening action bump landed in the release pipeline [4], and bash script fixes in cloud-provider-gcp [6] resolved issues with whitespace handling and vendor verification.

Action items

References

  1. [1] Merge pull request #136949 from sbueringer/pr-fix-managed-fields-purge kubernetes/apimachinery
  2. [2] Updating windows azure ccm and azuredisk periodic jobs to use capi templates from windows-testing ↗ kubernetes/test-infra
  3. [3] Add CBOR periodic ↗ kubernetes/test-infra
  4. [4] Merge pull request #4406 from kubernetes/dependabot/github_actions/actions-130119b845 kubernetes/release
  5. [5] metis: implement IPv6 Allocation in Metis Daemon ↗ kubernetes/cloud-provider-gcp
  6. [6] Bash script fixes ↗ kubernetes/cloud-provider-gcp

FAQ

What changed in Kubernetes on May 15, 2026?
Kubernetes patched a critical managedFields bug that was stripping data on conversion webhook failures, while test infrastructure begins a major migration to standardize Windows Azure testing across CAPZ.
What should Kubernetes teams do about it?
Pull the apimachinery managedFields patch into your next release if you use conversion webhooks • Track the Windows Azure test migration for status if you maintain CAPZ-dependent tests • Plan IPv6 testing in Metis if deploying dual-stack GCP clusters
Which Kubernetes repositories shipped on May 15, 2026?
kubernetes/apimachinery, kubernetes/test-infra, kubernetes/release, kubernetes/cloud-provider-gcp

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.