62a8394eb4
Automatic merge from submit-queue volume recycler: Don't start a new recycler pod if one already exists. Recycling is a long duration process and when the recycler controller is restarted in the meantime, it should not start a new recycler pod if there is one already running. This means that the recycler pod must have deterministic name based on name of the recycled PV, we then get name conflicts when creating the pod. Two things need to be changed: - recycler controller and recycler plugins must pass the PV.Name to place, where the pod is created. This is most of the patch and it should be pretty straightforward. - create recycler pod with deterministic name and check "already exists" error. When at it, remove useless 'resourceVersion' argument and make log messages starting with lowercase. There is an unit test to check the behavior + there is an e2e test that checks that regular recycling is not broken (it does not try to run two recycler pods in parallel as the recycler is single-threaded now). |
||
|---|---|---|
| .. | ||
| options | ||
| binder_test.go | ||
| controller_base.go | ||
| controller_test.go | ||
| controller.go | ||
| delete_test.go | ||
| framework_test.go | ||
| index_test.go | ||
| index.go | ||
| OWNERS | ||
| provision_test.go | ||
| recycle_test.go | ||
| volume_host.go | ||