*v1.Pod 的观看结束于：资源版本太旧
watch of *v1.Pod ended with: too old resource version
我将我的 EKS 从 1.16 更新到 1.17。突然间我开始收到这个错误：
pkg/mod/k8s.io/client-go@v0.0.0-20180806134042-1f13a808da65/tools/cache/reflector.go:99: watch of *v1.Pod ended with: too old resource version
查看 git，人们说这不是错误，但我的问题是如何停止接收这些消息？我在使用 EKS 1.16 时没有收到此消息？
这是一个社区维基答案。随意扩展它。
总之，遇到这些消息没什么好担心的。它们意味着在客户端 API 上次获取该监视 window 中的列表后，监视资源有较新版本。换句话说：针对 Kubernetes API 的监视超时，并且正在重新启动，这是预期的行为。
你也可以看到被提及here:
this is perfectly expected, no worries. The messages are several hours
apart.
When nothing happens in your cluster, the watches established by the
Kubernetes client don't get a chance to get refreshed naturally, and
eventually time out. These messages simply indicate that these watches
are being re-created.
和here:
these are nothing to worry about. This is a known occurrence in
Kubernetes and is not an issue [0]. The API server ends watch requests
when they are very old. The operator uses a client-go informer, which
takes care of automatically re-listing the resource and then
restarting the watch from the latest resource version.
所以回答你的问题：
my question is how to stop getting these messages
简单地说，你不会because:
This is working as expected and is not going to be fixed.
我将我的 EKS 从 1.16 更新到 1.17。突然间我开始收到这个错误：
pkg/mod/k8s.io/client-go@v0.0.0-20180806134042-1f13a808da65/tools/cache/reflector.go:99: watch of *v1.Pod ended with: too old resource version
查看 git，人们说这不是错误，但我的问题是如何停止接收这些消息？我在使用 EKS 1.16 时没有收到此消息？
这是一个社区维基答案。随意扩展它。
总之，遇到这些消息没什么好担心的。它们意味着在客户端 API 上次获取该监视 window 中的列表后，监视资源有较新版本。换句话说：针对 Kubernetes API 的监视超时，并且正在重新启动，这是预期的行为。
你也可以看到被提及here:
this is perfectly expected, no worries. The messages are several hours apart.
When nothing happens in your cluster, the watches established by the Kubernetes client don't get a chance to get refreshed naturally, and eventually time out. These messages simply indicate that these watches are being re-created.
和here:
these are nothing to worry about. This is a known occurrence in Kubernetes and is not an issue [0]. The API server ends watch requests when they are very old. The operator uses a client-go informer, which takes care of automatically re-listing the resource and then restarting the watch from the latest resource version.
所以回答你的问题：
my question is how to stop getting these messages
简单地说，你不会because:
This is working as expected and is not going to be fixed.