Trident Volume is stuck with a StatefulSet/Deployment Pod on a node that is down
radhika-pr opened this issue · 0 comments
radhika-pr commented
Describe the solution you'd like
I wanted to know if there is a similar feature available or being developed as Longhorn mentioned here.
The trident feature "enableForceDetach" does not detach the volume unless manually tainting the node and enabling non-graceful node shutdown on cluster. We want to have a feature which can detect the node failure(crash) scenario and automatic reassignment of volumes to available nodes (similar to above mentioned longhorn feature).
Describe alternatives you've considered
NA
Additional context
Add any other context or screenshots about the feature request here.