Fix watcher resourceVersion problem with 3.6 #855
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ok to test |
|
I've updated the endpoints used in mockwebserver to reflect the new behaviour of the watchers... crossing fingers 😉 |
|
add to whitelist |
|
@iocanel LGTM - you happy with it? |
|
[merge] |
This was referenced Jan 30, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix #852 by not using a resource version on the first call.
Since old versions of kubernetes, if you don't provide a resource version, the watch starts from the latest observed state, so there's no need to do a lookup before starting the watch.
Tested with Openshift origin 1.5 and 3.6.