Configure storage for Aerospike on Kubernetes

Aerospike Database supports several storage configurations.

Work directory and System MetaData (SMD)

Store the Aerospike work directory on persistent file system storage so System MetaData (SMD) files are retained across pod restarts. SMD holds cluster metadata such as secondary index definitions and security information.

Sample cluster Custom Resource (CR) files in the Aerospike Kubernetes Operator (AKO) repository include a persistent volume for the work directory. Define that volume in your cluster CR file under spec.storage.volumes, or under spec.rackConfig.racks[].storage.volumes when a rack overrides storage.

Configure storage

• Use flash memory for the Aerospike data and indexes: All Flash
• Test an Aerospike cluster without using separate storage: Data in Memory
• Use a provisioned SSD storage device: Data on SSD
• Store namespace data both in memory and on a persistent device: HDD Storage with Data in Memory
• Use the OpenEBS platform for persistent volume storage: OpenEBS
• Use high-performance local SSDs with a network-attached shadow device for data durability in cloud instances: Shadow Device
• Use persistent storage external to the Kubernetes pods: Storage Provisioning

Scaling

See Scaling Aerospike on Kubernetes for instructions on scaling storage after deployment.