RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

The Wire · Showcase

KOPS FIXES CASCADING GCP RESOURCE DELETION BUG AS HEALTH CHECK RECONCILIATION LANDS

By RepoJournal · Filed · About Kubernetes

KOps shipped critical fixes for GCP backend service ownership filtering that was causing infinite delete loops when clusters coexist with GKE, while simultaneously landing health check reconciliation logic across both GCP and AWS.

The GCP backend service ownership bug [1] was a nasty one: empty backend service lists were evaluated as vacuous truths, causing kOps to claim unrelated regional backend services in the same GCP project and their health checks, then get stuck in infinite delete retries. That's now fixed [2]. In parallel, kOps merged health check reconciliation for GCP [3] and AWS target group health checks [4] [5], which means cluster upgrades will now properly sync health check configuration changes without orphaning old resources. The AWS implementation [4] has already passed the k135-to-k136 upgrade test suite. On the core Kubernetes side, apiserver got cleanups: responsewriter benchmarks now reuse the exemplar pod fixture [6] [7] and watchCache code split into separate files [8] [9] for better maintainability. Minikube shipped configurable DNS servers for VM drivers [10], vmnet path fixes for Intel Macs [11], and bumped actions/checkout to 6.0.3 [12]. KEP-5793 advanced to beta in v1.37 [13] [14] and KEP-4794 got implementation history updates [15] [16]. Kubernetes added proper IPv6 and dual-stack allocator test coverage [17] [18] and updated DRA scheduler performance test cases [19].

Action items

References

  1. [1] gce: fix backend service ownership filtering during delete ↗ kubernetes/kops
  2. [2] Merge pull request #18460 from carterpewpew/fix/gce-backend-service-ownership kubernetes/kops
  3. [3] Merge pull request #18468 from hakman/gce-httphealthcheck-reconcile kubernetes/kops
  4. [4] aws: Reconcile target group health check changes on existing target groups ↗ kubernetes/kops
  5. [5] gce: Reconcile HTTP health check changes on existing health checks ↗ kubernetes/kops
  6. [6] Merge pull request #139664 from yedou37/cleanup-responsewriters-benchmarks kubernetes/apiserver
  7. [7] cleanup writers_test.go benchmarks to reuse existing exemplar pod ↗ kubernetes/kubernetes
  8. [8] Merge pull request #139704 from serathius/watchcache-split-files kubernetes/apiserver
  9. [9] Extract watchCacheHistory and watchCacheStorage to separate files ↗ kubernetes/kubernetes
  10. [10] Add configurable DNS servers for VM drivers ↗ kubernetes/minikube
  11. [11] vmnet: Fix brew install path on Intel Macs and support brew bin path ↗ kubernetes/minikube
  12. [12] Build(deps): Bump actions/checkout from 6.0.2 to 6.0.3 in the official-gh-actions group across 1 directory ↗ kubernetes/minikube
  13. [13] KEP-5793: update kep for beta in v1.37 ↗ kubernetes/enhancements
  14. [14] Merge pull request #6093 from aramase/aramase/d/kep_5793_beta_update kubernetes/enhancements
  15. [15] KEP-4794: update Implementation History, etc ↗ kubernetes/enhancements
  16. [16] Merge pull request #6193 from danwinship/kep-4974-updates kubernetes/enhancements
  17. [17] ipallocator: add IPv6 and dual-stack allocator tests ↗ kubernetes/kubernetes
  18. [18] Merge pull request #139706 from krishhna24/ipallocator-ipv6-dualstack-tests kubernetes/kubernetes
  19. [19] DRA: Update scheduler_perf integration test cases of ConsumableCapacity ↗ kubernetes/kubernetes

FAQ

What changed in Kubernetes on June 14, 2026?
KOps shipped critical fixes for GCP backend service ownership filtering that was causing infinite delete loops when clusters coexist with GKE, while simultaneously landing health check reconciliation logic across both GCP and AWS.
What should Kubernetes teams do about it?
Review and merge GCP backend service ownership fix if you run kOps with GKE coexistence • Test health check reconciliation changes in your AWS kOps upgrade pipeline before next cluster refresh • Update minikube if you need DNS server configuration on VM drivers
Which Kubernetes repositories shipped on June 14, 2026?
kubernetes/kops, kubernetes/apiserver, kubernetes/kubernetes, kubernetes/minikube, kubernetes/enhancements

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.