Volume Encryption

Longhorn supports encrypted volumes by utilizing the linux kernel module dm_crypt via cryptsetup for the encryption. Further we use the Kubernetes secret mechanism for key storage, which can be further encrypted and guarded via appropriate permissions. An encrypted volume results in your data being encrypted while in transit as well as at rest, this also means that any backups taken from that volume are also encrypted.

Requirements

To be able to use encrypted volumes, you will need to have the dm_crypt kernel module loaded and cryptsetup installed on your worker nodes.

Setting up Kubernetes Secrets

Volume encryption utilizes Kubernetes secrets for encryption key storage. To configure the secret that will be used for an encrypted volume, you will need to specify the secret as part of the parameters of a storage class. This mechanism is provided by Kubernetes and allows the usage of some template parameters that will be resolved as part of volume creation.

The template parameters can be useful in the case where you want to use a per volume secret or a group secret for a specific collection of volumes. More information about the available template parameters can be found in the Kubernetes documentation.

Example secret your encryption keys are specified as part of the CRYPTO_KEY_VALUE parameter. We use stringData as type here so we don’t have to base64 encoded before submitting the secret via kubectl create.

  1. ---
  2. apiVersion: v1
  3. kind: Secret
  4. metadata:
  5.   name: longhorn-crypto
  6.   namespace: longhorn-system
  7. stringData:
  8.   CRYPTO_KEY_VALUE: "Your encryption passphrase"
  9.   CRYPTO_KEY_PROVIDER: "secret"

Example storage class (global key for all volumes)

  1. kind: StorageClass
  2. apiVersion: storage.k8s.io/v1
  3. metadata:
  4.   name: longhorn-crypto-global
  5. provisioner: driver.longhorn.io
  6. allowVolumeExpansion: true
  7. parameters:
  8.   numberOfReplicas: "3"
  9.   staleReplicaTimeout: "2880" # 48 hours in minutes
  10.   fromBackup: ""
  11.   encrypted: "true"
  12.   # global secret that contains the encryption key that will be used for all volumes
  13.   csi.storage.k8s.io/provisioner-secret-name: "longhorn-crypto"
  14.   csi.storage.k8s.io/provisioner-secret-namespace: "longhorn-system"
  15.   csi.storage.k8s.io/node-publish-secret-name: "longhorn-crypto"
  16.   csi.storage.k8s.io/node-publish-secret-namespace: "longhorn-system"
  17.   csi.storage.k8s.io/node-stage-secret-name: "longhorn-crypto"
  18.   csi.storage.k8s.io/node-stage-secret-namespace: "longhorn-system"

Example storage class (per volume key)

  1. kind: StorageClass
  2. apiVersion: storage.k8s.io/v1
  3. metadata:
  4.   name: longhorn-crypto-per-volume
  5. provisioner: driver.longhorn.io
  6. allowVolumeExpansion: true
  7. parameters:
  8.   numberOfReplicas: "3"
  9.   staleReplicaTimeout: "2880" # 48 hours in minutes
  10.   fromBackup: ""
  11.   encrypted: "true"
  12.   # per volume secret which utilizes the `pvc.name` and `pvc.namespace` template parameters
  13.   csi.storage.k8s.io/provisioner-secret-name: ${pvc.name}
  14.   csi.storage.k8s.io/provisioner-secret-namespace: ${pvc.namespace}
  15.   csi.storage.k8s.io/node-publish-secret-name: ${pvc.name}
  16.   csi.storage.k8s.io/node-publish-secret-namespace: ${pvc.namespace}
  17.   csi.storage.k8s.io/node-stage-secret-name: ${pvc.name}
  18.   csi.storage.k8s.io/node-stage-secret-namespace: ${pvc.namespace}

Using an encrypted volume

To create an encrypted volume, you just create a PVC utilizing a storage class that has been configured for encryption. The above storage class examples can be used as a starting point.

After creation of the PVC it will remain in Pending state till the associated secret has been created and can be retrieved by the csi external-provisioner sidecar. Afterwards the regular volume creation flow will take over and the encryption will be transparently used so no additional actions are needed from the user.

Filesystem expansion

Longhorn supports offline expansion for encrypted volumes.

History

Available since v1.2.0 #1859