CNS can miss NNC updates when its watch is down #3278
Description
What happened:
CNS filters out NNC update events if a spec and status change are made while a watch is down.
What you expected to happen:
CNS should process added IPs to an NNC when it re-establishes its watch even if the spec has changed since the last time it saw it.
How to reproduce it:
Difficult to repro with CNS and NNCs. Better repro is to show that if you kill a watch on a controller and update a resource's spec and status, the controller will see 1 Update after it re-establishes the watch and the old and new object generations will be different.
Orchestrator and Version (e.g. Kubernetes, Docker):
Operating System (Linux/Windows):
Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]