✨ make sure vsphere cloud provider pod restart gracefully only on modify event

[XudongLiuHarold]

What this PR does / why we need it:

• ensure the pod restarting gracefully
• ensure the pod will only restart on watched file modify event

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1212

Special notes for your reviewer:

Release note:

NONE

[XudongLiuHarold]

team-cluster-api#25

[12345lcr]

Offline discussed with Xudong and this looks good to me. Perhaps only Remove event should be handled, since the watched file is a symlink and the link path is changed every time when the file is changed.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 12345lcr, XudongLiuHarold

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 [XudongLiuHarold]

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

[XudongLiuHarold]

/hold

Will do more tests to see if watch real files is a better approach for us

[XudongLiuHarold]

/hold cancel

I'd prefer keeping fsnotify to avoid a larger refactor for switching to viper

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale