auto remove the pv with hardware problems

[yuyulei]

What this PR does?

When the pv has a hardware problem,

1. If the pv is Bound state, some pod is using it, after migrating the affected pod to another node, we can delete pvc, so pv will beReleased state.
2. If the pv is Available state, after recycling the hardware, we have to manually delete broken pv.

Now, provisioner can do case 1, but can not handle case 2 automatically.
My pr is to solve it. If OK, I will add unit test.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: yuyulei
To complete the pull request process, please assign wongma7
You can assign the PR to them by writing /assign @wongma7 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @yuyulei. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[yuyulei]

/assign cofyc

[yuyulei]

/assign @wongma7

[yuyulei]

/cc cofyc

[yuyulei]

@cofyc @saad-ali

[cofyc]

hi, for security, we cannot simply delete the PV object if we failed to clean the directory.
the hardware problem may be a temporary issue, data in the volume may be leaked to other programs. Currently, admins must intervene when there are some hardware issues.

Possible solutions:

• fix the hardware issue and wait for the provisioner to clean the volume
• delete the PV object manually and make sure the data is cleaned (e.g. remove the hardware)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.