Loading
Version: Operator 3.4.0Use Data on SSD With Aerospike on Kubernetes
Overview
The following storage configuration sets up the Aerospike cluster to store namespace data on a provisioned SSD storage device.
For more information on storing namespace data on SSD and other storage configurations, see the Aerospike documentation for namespace storage configuration.
Setup
- Add the following storage-specific configuration to the Aerospike cluster's custom resource (CR) file.
storage:
filesystemVolumePolicy:
initMethod: deleteFiles
cascadeDelete: true
blockVolumePolicy:
cascadeDelete: true
volumes:
- name: workdir
aerospike:
path: /opt/aerospike
source:
persistentVolume:
storageClass: ssd
volumeMode: Filesystem
size: 1Gi
- name: ns
aerospike:
path: /test/dev/xvdf
source:
persistentVolume:
storageClass: ssd
volumeMode: Block
size: 5Gi
- name: aerospike-config-secret
source:
secret:
secretName: aerospike-secret
aerospike:
path: /etc/aerospike/secret
.
.
.
aerospikeConfig:
service:
feature-key-file: /etc/aerospike/secret/features.conf
security: {}
namespaces:
- name: test
replication-factor: 2
storage-engine:
type: device
devices:
- /test/dev/xvdf
For the full CR file, see the example SSD storage cluster CR.
This and other example CRs are in the main Aerospike Kubernetes Operator repository.
- Save and exit the CR file, then use
kubectl
to apply the change.
kubectl apply -f aerospike-cluster.yaml