bedrock

Storage classes

#Classes

bedrock’s two classes are defined in tenant-workload/storage/longhorn/.

longhorn-encryptedlonghorn-locallonghorn
Defined bylonghorn-encrypted.yamllonghorn-local.yamlLonghorn’s manifest
Default classNoNoYes
Replicas3, spread across nodes1Longhorn’s default, spread across nodes
Data localityOffstrict-localOff
EncryptedYes, LUKS with the key in longhorn-cryptoYes, LUKS with the key in longhorn-cryptoNo
BindingImmediateWaitForFirstConsumerImmediate
ExpansionAllowedAllowedAllowed
Reclaim policyDeleteDeleteDelete

longhorn-local binds only when the pod is scheduled, so the volume is created on the node the pod lands on, and strict-local keeps its one replica on that node. Garage and OpenBao run one pod per node, so each pod owns the disk beside it.

#Who uses which

ClassUsed by
longhorn-encryptedDatabase clusters, Prometheus, Loki, Tempo, Grafana, NATS, Valkey, Kafka
longhorn-localGarage, OpenBao
longhornNothing in bedrock

Garage replicates every object across its own nodes and OpenBao replicates its data over raft, so their volumes need no Longhorn replication. Everything else relies on Longhorn for its copies.

#Encryption key

Both encrypted classes pass the longhorn-crypto Secret to the CSI driver at stage, publish and expand time:

FieldValue
CRYPTO_KEY_PROVIDERsecret
CRYPTO_KEY_CIPHERaes-xts-plain64
CRYPTO_KEY_HASHsha256
CRYPTO_KEY_SIZE512
CRYPTO_PBKDFpbkdf2
CRYPTO_KEY_VALUEThe passphrase. Set it before the first deploy.

The classes have no provisioner secret parameters on purpose. Encryption happens on the node, so only the node stages need the key.

#Longhorn settings

tenant-workload/storage/longhorn/longhorn-settings.yaml changes these Longhorn defaults:

SettingValueWhy
node-down-pod-deletion-policydelete-both-statefulset-and-deployment-podPods on a dead node are deleted so they can start elsewhere with their volume
storage-over-provisioning-percentage300Volumes can promise more than the disk holds, since most are not full
upgrade-checkerfalseNo calls out to check for new versions
allow-collecting-longhorn-usage-metricsfalseNo usage data sent out