• Dmitry Shulyak's avatar
    Fix FakeNodeHandler Update behaviour · 0ddaa20b
    Dmitry Shulyak authored
    Two problems:
    1. Get is always using Existing nodes slice, and you will for sure miss any
       updated data
    2. Each Update duplicates node entry in UpdatedNodes slice
    
    For the 1st, try to find a node in UpdatedNodes slice (same as for the List).
    2nd - append only if there is no node with same name as updated, if there is
    just replace object.
    
    Change-Id: I9ef1cca2788ba946eee37fa1b037c124ad76074c
    0ddaa20b
Name
Last commit
Last update
..
admission Loading commit data...
api Loading commit data...
apimachinery Loading commit data...
apis Loading commit data...
apiserver Loading commit data...
auth Loading commit data...
capabilities Loading commit data...
client Loading commit data...
cloudprovider Loading commit data...
controller Loading commit data...
conversion Loading commit data...
credentialprovider Loading commit data...
dns Loading commit data...
fieldpath Loading commit data...
fields Loading commit data...
genericapiserver Loading commit data...
healthz Loading commit data...
httplog Loading commit data...
hyperkube Loading commit data...
kubectl Loading commit data...
kubelet Loading commit data...
kubemark Loading commit data...
labels Loading commit data...
master Loading commit data...
metrics Loading commit data...
probe Loading commit data...
proxy Loading commit data...
quota Loading commit data...
registry Loading commit data...
runtime Loading commit data...
security Loading commit data...
securitycontext Loading commit data...
selection Loading commit data...
serviceaccount Loading commit data...
ssh Loading commit data...
storage Loading commit data...
types Loading commit data...
ui Loading commit data...
util Loading commit data...
version Loading commit data...
volume Loading commit data...
watch Loading commit data...
OWNERS Loading commit data...