-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.16.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
No
-
None
-
None
-
None
-
CLOUD Sprint 258, CLOUD Sprint 259, CLOUD Sprint 260, CLOUD Sprint 261, CLOUD Sprint 263, CLOUD Sprint 264, CLOUD Sprint 262, CLOUD Sprint 265, CLOUD Sprint 266, CLOUD Sprint 267, CLOUD Sprint 268, CLOUD Sprint 269, CLOUD Sprint 270, CLOUD Sprint 271, CLOUD Sprint 272, CLOUD Sprint 273, CLOUD Sprint 274, CLOUD Sprint 275, CLOUD Sprint 276, CLOUD Sprint 277, CLOUD Sprint 278
-
21
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
kube-controller-manager operator is cleaning up resources for legacy in-tree controllers, running multiple delete requests to apiserver.
This has several drawbacks:
* API Server can't cache DELETE requests, so it has to request etcd every time
* Audit log is flooded with "delete failed: object 'foo' not found" record
The function should first check that the object exists (GET requests are cachable) before issuing a DELETE request
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
