node-driver-registrar icon indicating copy to clipboard operation
node-driver-registrar copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-csi

Node Driver Registrar restart at GetDriverName call

Open Anto74 opened this issue 9 months ago • 2 comments

Hi there,

node-driver-registrar integrated in my CSI driver restarted a number of time at install, upgrade, node server pod restart.

Logs show the following: E0427 17:58:20.335386 8 main.go:170] error retreiving CSI driver name: rpc error: code = DeadlineExceeded desc = context deadline exceeded

I use one second default value for timeout duration (--timeout parameter).

My customer requirement is to limit restarts as much as possible, with the aim to have no restart at all for any containers. So, I tried two seconds and I managed to avoid restarts. Anyway, it is not possible to be sure that two seconds timeout is always enough.

Is there any reason why node driver registrar container performs os.Exit(1) (causing restart) at first timeout without retrying? Is it possible to consider the opportunity to introduce a configurable number of reattempts?

Thanks in advance and best regards, Antonio

Anto74 avatar May 10 '24 08:05 Anto74