-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
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
UPSTREAM: 24208: Honor starting resourceVersion in watch cache #8514
Conversation
This wasn't a clean cherry-pick. Please review carefully. I assume we'll want to wait for this to merge upstream |
The only "sane" way I could see to do this would be to explicitly depend on the comparability of resourceVersions when used by etcd. I didn't know that was a restriction for this. Is it? Is that limitation well known? |
@deads2k I'm not sure what you're asking |
But better to comment on the upstream PR, right? |
yes, the assumption of resourceVersion comparability runs throughout the watch cache |
LGTM |
Upstream PR just merged |
[merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/5593/) (Image: devenv-rhel7_3973) |
[merge] |
@miminar @smarterclayton does the flake above look familiar? |
Evaluated for origin merge up to 66d1fdd |
yeah, #8399 |
@liggitt @smarterclayton