The resourceVersion for the provided watch is too old.

[jicki]

• kubernetes 1.13.1
• etcd Version: 3.2.24

Dec 19 14:20:18 kubernetes-1 etcd: finished scheduled compaction at 287899 (took 880.318µs)
Dec 19 14:20:42 kubernetes-1 kube-apiserver: E1219 14:20:42.734560   16692 watcher.go:208] watch chan error: etcdserver: mvcc: required revision has been compacted
Dec 19 14:20:42 kubernetes-1 kube-controller-manager: W1219 14:20:42.734797   16725 reflector.go:270] k8s.io/client-go/informers/factory.go:132: watch of *v1beta1.Event ended with: The resourceVersion for the provided watch is too old.

[k8s-ci-robot]

@jicki: There are no sig labels on this issue. Please add a sig label by either:

1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
   e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

2. specifying the label manually: /sig <group-name>
   e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[liggitt]

this is working as designed. attempts to re-establish a watch from a resourceVersion that is no longer available return a 410 Gone error, prompting the caller to re-list objects and obtain a new current resourceVersion to watch from

/close

[k8s-ci-robot]

@liggitt: Closing this issue.

In response to this:

this is working as designed. attempts to re-establish a watch from a resourceVersion that is no longer available return a 410 Gone error, prompting the caller to re-list objects and obtain a new current resourceVersion to watch from

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.