We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The watch loop in Watcher should send the newest resourceVersion it has seen when restarting the watch connection to reduce pressure on the apiserver. See https://kubernetes.io/docs/reference/using-api/api-concepts/#efficient-detection-of-changes for suggested behavior.
This mechanism should probably be extended to support the watch bookmark feature (https://kubernetes.io/docs/reference/using-api/api-concepts/#watch-bookmarks) if available (since Kubernetes 1.16).
The text was updated successfully, but these errors were encountered:
Watch bookmark KEP: https://github.com/kubernetes/enhancements/blob/239b0c8cc09895b63151806251d7f6c2d2c3aa2f/keps/sig-api-machinery/20190206-watch-bookmark.md
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The watch loop in Watcher should send the newest resourceVersion it has seen when restarting the watch connection to reduce pressure on the apiserver. See https://kubernetes.io/docs/reference/using-api/api-concepts/#efficient-detection-of-changes for suggested behavior.
This mechanism should probably be extended to support the watch bookmark feature (https://kubernetes.io/docs/reference/using-api/api-concepts/#watch-bookmarks) if available (since Kubernetes 1.16).
The text was updated successfully, but these errors were encountered: