Skip to content

longhorn/longhorn-manager

master
Switch branches/tags
Code

Latest commit

The validation failure while syncing configmap to setting CRs will lead to
that the longhorn-manager cannot start successfully.
To avoid the failure, the unavailable default settings are filtered and
only sync the available ones.

Longhorn 4160

Signed-off-by: Derek Su <derek.su@suse.com>
ddf1b8d

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
May 3, 2017

Longhorn Manager

Build StatusGo Report Card

Manager for Longhorn.

Requirement

  1. Existing Kubernetes Cluster 1.16+.
  2. Make sure iscsiadm/open-iscsi has been installed on the host.

Build

make

Deployment

kubectl create -Rf deploy/install

It will deploy the following components in the longhorn-system namespace:

  1. Longhorn Manager
  2. Longhorn Flexvolume Driver for Kubernetes
  3. Longhorn UI

Cleanup

Longhorn CRD has finalizers in them, so user should delete the volumes and related resource first, give manager a chance to clean up after them.

To prevent damage to the Kubernetes cluster, we recommend deleting all Kubernetes workloads using Longhorn volumes (PersistentVolume, PersistentVolumeClaim, StorageClass, Deployment, StatefulSet, DaemonSet, etc).

  1. Create the uninstallation job to cleanly purge CRDs from the system and wait for success:
kubectl create -f deploy/uninstall/uninstall.yaml
kubectl get job/longhorn-uninstall -w

Example output:

$ kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/uninstall/uninstall.yaml
serviceaccount/longhorn-uninstall-service-account created
clusterrole.rbac.authorization.k8s.io/longhorn-uninstall-role created
clusterrolebinding.rbac.authorization.k8s.io/longhorn-uninstall-bind created
job.batch/longhorn-uninstall created

$ kubectl get job/longhorn-uninstall -w
NAME                 COMPLETIONS   DURATION   AGE
longhorn-uninstall   0/1           3s         3s
longhorn-uninstall   1/1           20s        20s
^C
  1. Remove remaining components:
kubectl delete -Rf deploy/install
kubectl delete -f deploy/uninstall/uninstall.yaml

Tip: If you try kubectl delete -Rf deploy/install first and get stuck there, pressing Ctrl C then running kubectl create -f deploy/uninstall/uninstall.yaml can also help you remove Longhorn. Finally, don't forget to cleanup remaining components by running kubectl delete -f deploy/uninstall/uninstall.yaml.

Integration test

See longhorn-tests repo

Contribution

Please check the Longhorn repo for the contributing guide.

License

Copyright (c) 2014-2021 The Longhorn Authors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

About

Millions and millions of volumes orchestrated

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages