False update events during rolling update #3
Description
During a rolling update of a k8s cluster (especially when it's somehow stuck), there could be a situation when the browser loads client-side code from a pod running the new version, but then /version.json is served by a pod running the previous version, which will generate a false update event. There should be a way/recipe to handle this with some kind of linear order comparison.