1
0
Fork 0
kubernetes/storage
Dustin 0a6086eb2a longhorn: Run on dedicated nodes
I've created new worker nodes that are dedicated to running Longhorn
replicas.  These nodes are tainted with the
`node-role.kubernetes.io/longhorn` taint, so no regular pods will be
scheduled there by default.  Longhorn pods thus needs to be configured
to tolerate that taint, and to be scheduled on nodes with the
similarly-named label.
2024-11-21 22:59:14 -06:00
..
.gitignore storage: Add Longhorn backup target secret 2024-10-13 14:03:49 -05:00
README.md storage: Use Authelia for Longhorn UI auth 2023-01-13 21:33:14 -06:00
longhorn-ingress.yaml storage: Use Authelia for Longhorn UI auth 2023-01-13 21:33:14 -06:00
longhorn-settings.yaml longhorn: Run on dedicated nodes 2024-11-21 22:59:14 -06:00
longhorn.yaml longhorn: Run on dedicated nodes 2024-11-21 22:59:14 -06:00
minio-backups-credentials.yaml storage: Add Longhorn backup target secret 2024-10-13 14:03:49 -05:00

README.md

Persistent Storage Using Longhorn

Longhorn is a Kubernetes-native persistent storage system. It is quite complex, but installing it is fairly straightforward.

Installation

This is mostly based on the official Install with Kubectl instructions. I wanted to add node selectors to the user-deployed and system-managed components, to ensure that Longhorn only runs on x86_64 nodes, per the Node Selector instructions.

kubectl apply -f longhorn.yaml

Ingress

Expose the Longhorn UI outside the cluster:

kubectl apply -f longhorn-ingress.yaml

Authentication to the UI is handled by Authelia.