With Longhorn, you can specify the size of the volume, the number of synchronous replicas and other volume specific configurations you want across the hosts that supply the storage resource for the volume. Instead, the workloads’ storage requirements should be defined in Kubernetes Persistent Volumes (PVs) and Persistent Volume Claims (PVCs). Pods can reference storage directly, but this is not recommended because it doesn’t allow the Pod or container to be portable. Use Persistent Storage in Kubernetes without Relying on a Cloud Provider The Longhorn Manager component orchestrates the Longhorn Engines, so they work together coherently. The controller is called the Longhorn Engine. By using one storage controller per volume, Longhorn turns each volume into a microservice. By contrast, Longhorn can simplify the storage system by partitioning a large block storage controller into a number of smaller storage controllers, as long as those volumes can still be built from a common pool of disks. Simplifying Distributed Block Storage with Microservicesīecause modern cloud environments require tens of thousands to millions of distributed block storage volumes, some storage controllers have become highly complex distributed systems. Longhorn comes with a standalone UI, and can be installed using Helm, kubectl, or the Rancher app catalog. Upgrade Longhorn without disrupting persistent volumes.Schedule recurring snapshots of a volume, and schedule recurring backups to NFS or S3-compatible secondary storage.Create cross-cluster disaster recovery volumes so that data from a primary Kubernetes cluster can be quickly recovered from backup in a second Kubernetes cluster.Store backup data in external storage such as NFS or AWS S3.Replicate block storage across multiple nodes and data centers to increase availability.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |