Kubernetes v1.36 introduces staleness mitigation and observability features to address outdated controller caches.
- •Atomic FIFO processing in client-go ensures consistent queue states when events arrive out of order
- •New LastStoreSyncResourceVersion() function enables controllers to check if their cache has latest cluster state
- •DaemonSet, StatefulSet, ReplicaSet, and Job controllers validate cache freshness before reconciliation by default
- •ConsistencyStore interface provides WroteAt(), EnsureReady(), and Clear() methods for custom staleness mitigation
- •Metrics like stale_sync_skips_total and store_resource_version provide visibility into controller cache consistency
This summary was automatically generated by AI based on the original article and may not be fully accurate.