It is responsible for creating and managing volumes in the Kubernetes cluster, and handles the API calls from the UI or the volume plugins for Kubernetes. The Longhorn Manager Pod runs on each node in the Longhorn cluster as a Kubernetes DaemonSet. The Longhorn Manager and the Longhorn Engine The Longhorn Engine is a storage controller that corresponds to the data plane, and the Longhorn Manager corresponds to the controlplane. The Longhorn design has two layers: the data plane and the controlplane. Horizontal Scaling for Kubernetes Workloads with Persistent Storage.How Kubernetes Workloads use New and Existing Persistent Storage.Appendix: How Persistent Storage Works in Kubernetes.Backupstore Update Intervals, RTO and RPO How Read and Write Operations Work for Replicas Advantages of a Microservices Based Design For help with the terminology used in this page, refer to this section. For more information on these concepts, refer to the appendix. This section assumes familiarity with Kubernetes persistent storage concepts. The storage controller and replicas are themselves orchestrated using Kubernetes.įor an overview of Longhorn features, refer to this section.įor the installation requirements, go to this section. Longhorn creates a dedicated storage controller for each volume and synchronously replicates the volume across multiple replicas stored on multiple nodes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |