fix: don't ignore kubernetes API access failure during node taint removal

[steved]

Is this a bug fix or adding new feature?

Bug fix

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

Prior to #1287, it made sense to not fail initialization if the driver could not talk to the K8s API. Now that it's being retried, it shouldn't silently fail if the K8s API isn't accessible.

What testing is done?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: steved
Once this PR has been reviewed and has the lgtm label, please assign ashley-wenyizha for approval. For more information see the Kubernetes Code Review Process.

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 @steved. 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-sigs/prow repository.

[steved]

bump - @mskanth972 any thoughts?

[steved]

/assign @mskanth972