optimize force drain node and delete cluster

[x893675]

Signed-off-by: x893675 x893675@icloud.com

What type of PR is this?

/kind optimize

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

[kubeclipper-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: x893675

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [x893675]

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

[x893675]

/cc @zhuzhenfan

[zhuzhenfan]

/lgtm

[kubeclipper-bot]

LGTM label has been added.

Git tree hash: 7dd194ea405e420d7cfa1617673cba57ea416a1c

[x893675]

/cherrypick master

[kubeclipper-bot]

@x893675: #382 failed to apply on top of branch "master":

Applying: optimize force drain node and delete cluster
Using index info to reconstruct a base tree...
M	pkg/apis/core/v1/handler.go
M	pkg/apis/core/v1/utils.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/apis/core/v1/utils.go
Auto-merging pkg/apis/core/v1/handler.go
CONFLICT (content): Merge conflict in pkg/apis/core/v1/handler.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 optimize force drain node and delete cluster
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick master

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.

[kubeclipper-bot]

@x893675: new issue created for failed cherrypick: #384

In response to this:

/cherrypick master

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.