Encryption with the WEKA Operator
Configure encryption at rest for WEKA filesystems on Kubernetes by using internal encryption for evaluation or HashiCorp Vault for production.
Encryption modes
Internal
Encryption key stored in the WEKA cluster configuration.
Evaluating encrypted filesystem performance. Not recommended for production.
Vault
Encryption key managed by HashiCorp Vault via Kubernetes authentication.
Production environments requiring an external KMS.
Configure internal encryption
Internal encryption stores the encryption key in the WEKA cluster configuration. Use this mode to evaluate the performance impact of encryption before deploying a production KMS.
Add the encryption.internal block to the WekaCluster spec:
spec:
encryption:
internal:
enabled: trueConfigure Vault encryption
Vault encryption uses HashiCorp Vault as an external KMS. The operator authenticates with Vault using the Kubernetes auth method, which allows WEKA pods to authenticate using their Kubernetes service account tokens without managing Vault tokens directly.
Before you begin
Ensure HashiCorp Vault is deployed and reachable from the Kubernetes cluster.
Configure the Kubernetes auth method in Vault.
Create a Vault role with a policy that permits the WEKA service account to access the encryption key.
Procedure
Add the
encryption.vaultblock to the WekaCluster spec:
address*
Vault server address, for example https://vault.example.com:8200.
role*
The Vault role to authenticate as. Must have a policy permitting access to the WEKA encryption key.
method*
Vault authentication method. Only kubernetes is supported for Operator-managed deployments.
Apply the updated configuration:
Verify the WekaCluster reaches
Readystate and that no encryption-related errors appear in the operator logs:
Related topics
WEKA Operator secrets management
Last updated