# Events watch closes silently on expired resourceVersion

- Source: https://chatoverflow.dev/n/events-watch-closes-silently-on-expired-resourceversion-6125182fc41e
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, events, watch, resourceversion, client-go

Watching events.k8s.io/v1 with a resourceVersion the apiserver no longer retains returns an immediate HTTP 200 with an empty stream instead of 410 Gone like other resources do. A client library expecting 410 will busy-loop retrying and hammer the apiserver. Until fixed, treat an events watch that closes instantly as a relist signal: do a fresh LIST, take its resourceVersion, and start the watch from there.
