Aerospike

Detailed information on the Aerospike state store component

Setup Aerospike

You can run Aerospike locally using Docker:

  1. docker run -d --name aerospike -p 3000:3000 -p 3001:3001 -p 3002:3002 -p 3003:3003 aerospike

You can then interact with the server using localhost:3000.

The easiest way to install Aerospike on Kubernetes is by using the Helm chart:

  1. helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
  2. helm install --name my-aerospike --namespace aerospike stable/aerospike

This will install Aerospike into the aerospike namespace. To interact with Aerospike, find the service with: kubectl get svc aerospike -n aerospike.

For example, if installing using the example above, the Aerospike host address would be:

aerospike-my-aerospike.aerospike.svc.cluster.local:3000

Create a Dapr component

The next step is to create a Dapr component for Aerospike.

Create the following YAML file named aerospike.yaml:

  1. apiVersion: dapr.io/v1alpha1
  2. kind: Component
  3. metadata:
  4. name: <NAME>
  5. namespace: <NAMESPACE>
  6. spec:
  7. type: state.Aerospike
  8. version: v1
  9. metadata:
  10. - name: hosts
  11. value: <REPLACE-WITH-HOSTS> # Required. A comma delimited string of hosts. Example: "aerospike:3000,aerospike2:3000"
  12. - name: namespace
  13. value: <REPLACE-WITH-NAMESPACE> # Required. The aerospike namespace.
  14. - name: set
  15. value: <REPLACE-WITH-SET> # Optional.

Warning

The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.

Apply the configuration

In Kubernetes

To apply the Aerospike state store to Kubernetes, use the kubectl CLI:

  1. kubectl apply -f aerospike.yaml

Running locally

To run locally, create a components dir containing the YAML file and provide the path to the dapr run command with the flag --components-path.

Last modified February 16, 2021: Merge pull request #1235 from dapr/update-v0.11 (b4e9fbb)