In order to be able to manage Netapp Trident persistent volumes, the Trident backend should be online.
If for some reason we lose the connection between the Trident controller and the NetApp SVM even for a few seconds, the backend will go to a failed state and will never go back online by itself, even if the connection is restored.
To resume an online state for the backend, we need to evacuate or recreate the controller replica set in order to refresh the configuration.
We like to have some sort of scheduled job that runs every x seconds to check if the SVM is reachable. and if that's the case, the backend should automatically go back online; if not, it remains failed.
Describe the solution you'd like
In order to be able to manage Netapp Trident persistent volumes, the Trident backend should be online.
If for some reason we lose the connection between the Trident controller and the NetApp SVM even for a few seconds, the backend will go to a failed state and will never go back online by itself, even if the connection is restored.
To resume an online state for the backend, we need to evacuate or recreate the controller replica set in order to refresh the configuration.
We like to have some sort of scheduled job that runs every x seconds to check if the SVM is reachable. and if that's the case, the backend should automatically go back online; if not, it remains failed.