2ddeb94b56
All objects with graceful deletion allow multiple DELETE calls in the pending state. Namespace is the one outlier, and the error here predates graceful deletion and finalizers. We should make this behavior consistent with other calls and merely indicate success and return the state of the object, the same as if there were pending metadata finalizers. Clients that previously checked for a conflict error during delete to know that the server is already deleting will now no longer receive an error (as if the object were rapidly deleted). There is a small chance that some clients have error checking for this state, but a much larger chance that clients that want to trigger a delete of the namespace do not handle this error case. Discovered in an e2e test that used the framework namespace and triggered deletion of that ns itself, and then the AfterEach step in e2e failed because the namespace was already pending deletion. |
||
|---|---|---|
| .. | ||
| storage | ||
| BUILD | ||
| doc.go | ||
| strategy_test.go | ||
| strategy.go | ||