Daniel Smith

Depending on the encryption at rest implementation, listing all secrets could be a very expensive operation. It could be optimized, but no one has done so yet. Also note that...

> "killing connection/stream because serving request timed out and response had been started" This is proof that you're hitting the 60s global time out I mentioned previously. The client needs...

sorry I didn't see this the first time around -- why do we need this change? It seems to cause no generated code changes? Is it blocking a PR here...

> The alternative pattern that I've seen us adopt (I believe) is not to write to the cache, and simply to operate on changes as the cache observes them, waiting...

> how deletes would work with option 2 (since resetting the object version would be confusing to clients) Clients already have to watch for UID changes. Yes, it would reset...

> Also: We should check with all the aggregated apiserver implementations, as I think they are free to use strings if it makes them happy. I would not say they...

Both, but not everyone has the interobject ("cross-object" in the OP) ordering problem. > Option 1 invites users to write logic that attempts to handle interobject ordering, but I fear...

@justinsb the problem is with controllers that list all objects of some type and then do something with that. If one object has gone forward in time, some other number...

@stevekuznetsov It does (ish), see this bullet point: > More difficult to solve the cross-object ordering problem (**you have to wait for object X to hit at least objectVersion Y,...

@stevekuznetsov You have to assume that the watch events haven't been reordered.