Fix: [node-cleanup] Check node label to know if pv is linked to a deleted node

[Fricounet]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The current implementation of the node cleanup controller has a bug where if the kubernetes.io/hostname in the affinity of the PV is not the same as the node.Name, all the local PV and PVC will be considered as being linked to a deleted node and be deleted. We have this situation on AWS clusters where the label is kubernetes.io/hostname: ip-10-10-10-10 but the node name is ip-10-10-10-10.ec2.internal. This PR changes how the controller look for the node to now rely on the label on the node rather than the node name.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Release note:

[k8s-ci-robot]

Welcome @Fricounet!

It looks like this is your first PR to kubernetes-sigs/sig-storage-local-static-provisioner 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/sig-storage-local-static-provisioner has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

[k8s-ci-robot]

Hi @Fricounet. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[andyzhangx]

/ok-to-test

[Fricounet]

@andyzhangx do you think you could take a look at this PR when you have some time?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, Fricounet

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~~ [andyzhangx]

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