Wojciech Tyczynski

We definitely need more info to debug it. I would also add that watchcache is propagate with reflector, so I think that if the issue exists, it's may potentially happen...

Hmm - it seems that this might be a problem around guarantees for PrevKey @serathius can provide more details here @mborsz - FYI

> cc @aojea for suggestions how to best test it. @serathius - The only reasonable suggestion that I have is to create a mock client and have unit test with...

@jpbetz @shyamjvs - I'm actually also on the fence with it: 1) on one hand I actually agree that in case of issues, we need some mechanism to be able...

I just chatted with Marek about this and the other option is: 8) Expose this option only as an internal API - we have a precedent for something like this...

> anything that our kube-apiserver accepts header-wise becomes part of our API whether we expose it in client-go or not. So adding a header without the corresponding Options change makes...

FWIW - I'm trying to revisit this decision in https://github.com/kubernetes/enhancements/pull/4608

/cc

/remove-label lifecycle/state

/lgtm /approve