Use HDD Storage with Data in Memory for Aerospike on Kubernetes

Overview

This example lets you store namespace data both in memory and on the persistent device. For more information on setting up HDD storage with data-in-memory and other storage configurations, see the Aerospike documentation for namespace storage configuration.

Configure HDD storage

1. Add the following storage-specific configuration to the Aerospike cluster’s CR file.

     storage:
       filesystemVolumePolicy:
         cascadeDelete: false
         initMethod: deleteFiles
       volumes:
         - name: workdir
           aerospike:
             path: /opt/aerospike
           source:
             persistentVolume:
               storageClass: ssd
               volumeMode: Filesystem
               size: 1Gi
         - name: ns
           aerospike:
             path: /opt/aerospike/data
           source:
             persistentVolume:
               storageClass: ssd
               volumeMode: Filesystem
               size: 3Gi
         - 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: {}
       namespace:
         - name: test
           replication-factor: 2
           storage-engine:
             type: memory
             file:
               - /opt/aerospike/data/test.dat
             filesize: 2000000000

   For the full CR file, see the example HDD storage with data-in-memory cluster CR.

   This and other example CRs are available in the main Aerospike Kubernetes Operator repository.

2. Save and exit the CR file, then use kubectl to apply the change.

   kubectl apply -f aerospike-cluster.yaml