Timeout limit in Connect() function is leading to crashloopbackoff of controller pod of CSI-Driver. #162
Labels
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
We were going through with this PR and have found that @ConnorJC3 and team has introduced a timeout limit as part of bbcd132.
Can someone please provide insight into the rationale behind implementing this timeout?
Given that many CSI-sidecars rely on this utility, imagine a scenario with two controllers where only one is the leader. In such a case, the non-leading controller is unable to connect. In the previous setup with an infinite timeout, the controllers attempted to establish a connection indefinitely. As a result, the controller pod remained in a running state, avoiding crashloopbackoff.
Once the pod assumed the leader role, the session was established seamlessly but because of this change now pod is in crashloopbackoff.
Tasks
The text was updated successfully, but these errors were encountered: