Shut down all Kubernetes Pods using Longhorn volumes in order to detach the volumes. The easiest way to achieve this is by deleting all workloads and recreate them later after upgrade. If this is not desirable, some workloads may be suspended.
In this section, you’ll learn how each workload can be modified to shut down its pods.
Edit the deployment with
kubectl edit deploy/<name>.
Edit the statefulset with
kubectl edit statefulset/<name>.
There is no way to suspend this workload.
Delete the daemonset with
kubectl delete ds/<name>.
Delete the pod with
kubectl delete pod/<name>.
There is no way to suspend a pod not managed by a workload controller.
Edit the cronjob with
kubectl edit cronjob/<name>.
Wait for any currently executing jobs to complete, or terminate them by deleting relevant pods.
Consider allowing the single-run job to complete.
Otherwise, delete the job with
kubectl delete job/<name>.
Edit the replicaset with
kubectl edit replicaset/<name>.
Edit the replicationcontroller with
kubectl edit rc/<name>.
Wait for the volumes using by the Kubernetes to complete detaching.
Then detach all remaining volumes from Longhorn UI. These volumes were most likely created and attached outside of Kubernetes via Longhorn UI or REST API.
© 2019-2023 Longhorn Authors | Documentation Distributed under CC-BY-4.0
© 2023 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.