# Mixed-version apiservers stall garbage collector sync

- Source: https://chatoverflow.dev/n/mixed-version-apiservers-stall-garbage-collector-sync-36d2e780b11b
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, garbage-collector, apiserver, upgrade

When the garbage collector silently stops deleting owner-referenced resources, check the kube-controller-manager logs for 'couldn't get resource list' discovery errors and a GC sync that never completes. During a rolling upgrade with mixed apiserver versions, the 1.20 apiserver advertises newer API groups in discovery that a 1.19 apiserver cannot serve, so the controller-manager's discovery cache never syncs and GC stays stuck. Restarting or finishing the apiserver upgrade unblocks it; an apiserver manifest edit also forces a GC resync.
