make sure the startup taint will eventually being removed after efs driver ready

[abbshr]

Is this a bug fix or adding new feature?

bug fix

What is this PR about? / Why do we need it?

removeNotReadyTaint() just call one time, so there may be accident the taint didn't remove successfully,
lead to node unschedulable for the pod can't tolerate the taint, this PR make sure the startup taint will eventually being removed after efs driver ready.

What testing is done?
test the compensation mechanism

[linux-foundation-easycla]

• ✅login: abbshr / (6ef167b)
• ✅login: abbshr / (6ef167b, 4e270c4)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @abbshr!

It looks like this is your first PR to kubernetes-sigs/aws-efs-csi-driver 🎉. 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/aws-efs-csi-driver 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. 😃

[k8s-ci-robot]

Hi @abbshr. 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.

[seanzatzdev-amazon]

/ok-to-test

[seanzatzdev-amazon]

Thank you for raising this PR @abbshr , as mentioned by the bot above, please follow the CLA authorization process here: #1287 (comment)

Believe this PR should address the following issue: #1320

[CMaylone]

Hello, anything I can help do in order to get this merged? We have experienced the taint not being cleared in our clusters and have a temp hack in place to mitigate the issue. We would love to use this fix instead!

[abbshr]

Signed CLA~

/cc @seanzatzdev-amazon

[seanzatzdev-amazon]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abbshr, seanzatzdev-amazon

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 [seanzatzdev-amazon]

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

[MrMarkW]

When will this get released?

[mskanth972]

Hi @abbshr, we are trying to release this PR. We have cherry picked this commit but bot prompts that these commits were not CLA authorized. Can you resolve that. For example below,
#1389

[abbshr]

Hi @abbshr, we are trying to release this PR. We have cherry picked this commit but bot prompts that these commits were not CLA authorized. Can you resolve that. For example below, #1389

@mskanth972 Done

[mamoit]

Even with the latest efs-csi-driver version we're still getting lingering taints even though the driver logs state that the taints were removed.