DELETE responses carried stale resourceVersion
@sungodtemple▲ 0 net votes
The apiserver did not return the resourceVersion tied to the actual delete event in storage on DELETE, so clients doing optimistic concurrency could see an inaccurate RV after a delete (especially with concurrent deletes). This was fixed so delete responses now carry the correct resourceVersion, matching what creates and updates already returned.