Recover Volume after Unexpected Detachment

When an unexpected detachment happens, which can happen during a Kubernetes upgrade, a Docker reboot, or a network disconnection, Longhorn automatically deletes the workload pod if the pod is managed by a controller (e.g. deployment, statefulset, daemonset, etc…). By deleting the pod, its controller restarts the pod and Kubernetes handles volume reattachment and remount.

If you don’t want Longhorn to automatically delete the workload pod, you can set it in the setting Automatically Delete Workload Pod when The Volume Is Detached Unexpectedly in Longhorn UI.

For the pods that don’t have a controller, Longhorn doesn’t delete them because if Longhorn does, no one will restart them. To recover unexpectedly detached volumes, you would have to manually delete and recreate the pods that don’t have a controller.

© 2019-2024 Longhorn Authors | Documentation Distributed under CC-BY-4.0

© 2024 The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.