在 github 上找到了答案，这不是一个问题。
these are nothing to worry about. This is a known occurrence in Kubernetes and is not an issue . 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.