Kubelet plugin registration should retry on failures

[saad-ali]

What happened:

If kubelet plugin registration fails during the registration process, the kubelet never attempts to register the socket again (assuming the error was transient), unless the socket for the driver is deleted & recreated to trigger a new registration.

What you expected to happen:
Maybe retry with exponential backoff when kubelet plugin registration fails instead of just logging and waiting for another filesystem event like it does today.

Of course, if a socket returns a terminal error (does not implement the kubelet plugin registration service, for example), we should not retry.

Follow up on #71440

/milestone v1.14
/sig storage

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

/kind bug

[taragu]

@saad-ali I'd like to work on this issue

[taragu]

/assign

[saad-ali]

Re opening.

#72873 was a temporary work around for this.

#73891 is the permanent fix.

[dstrebel]

Hello! We are starting Bug Freeze for 1.15. Is this issue still planned on being incorporated into 1.15?

[taragu]

@dstrebel the dependent PR #73891 is not yet merged. @saad-ali can we get this in for 1.15?

[dims]

@saad-ali said that #73891 is the "permanent fix." and that has merged. So let's close this out

/close

[k8s-ci-robot]

@dims: Closing this issue.

In response to this:

@saad-ali said that #73891 is the "permanent fix." and that has merged. So let's close this out

/close

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.