This project uses Aerospike Server Community Edition. For Aerospike Server Enterprise Edition, please refer aerospike/aerospike-kubernetes-enterprise.
This project contains the init container used in Kubernetes (k8s) and the Aerospike StatefulSet definition. These manifests will allow you to deploy a fully formed Aerospike cluster in minutes.
It uses:
Set environment variables (modify if necessary):
export APP_NAME=aerospike
export NAMESPACE=default
export AEROSPIKE_NODES=3
export AEROSPIKE_NAMESPACE=test
export AEROSPIKE_REPL=2
export AEROSPIKE_MEM=1
export AEROSPIKE_TTL=0
export AEROSPIKE_NSUP_PERIOD=0 # if AEROSPIKE_TTL is not 0, AEROSPIKE_NSUP_PERIOD should not be 0.
All AEROSPIKE_*
parameters except AEROSPIKE_NODES, AEROSPIKE_MEM are optional. Default values are listed above.
All other parameters are required.
The statefulset definition refers to a custom StorageClass ssd
.
You can find the storageclass ssd
definition in storageclass-aws.yaml or storageclass-gcp.yaml (Uncomment them to use). You can also define your own storageclass and use it within the statefulset definition.
Dynamic provisioning for local volumes are not supported yet. However, a local volume provisioner can be deployed to automate the provisioning of local devices. Please check
examples/
for using a local volume static provisioner.
If you want to use the raw block volume mode, you need to define volumeMode
as Block
in the Volume Claim and use volumeDevices
and devicePath
instead of volumeMounts
and mountPath
as shown in the example below.
volumeClaimTemplates:
- metadata:
name: data-dev
labels: *AerospikeDeploymentLabels
spec:
volumeMode: Block
accessModes:
- ReadWriteOnce
storageClassName: ssd
resources:
requests:
storage: ${AEROSPIKE_MEM}Gi
.....
volumeMounts:
- name: confdir
mountPath: /etc/aerospike
volumeDevices:
- name: data-dev
devicePath: /dev/sdb
.....
For Kubernetes version > 1.11, there's a default storage class gp2
available on AWS EKS clusters, uses aws-ebs
provisioner and volume type gp2
.
To view and run the examples, go to examples/
Please follow the below steps or run start.sh
script:
- Expand manifest template:
cat manifests/* | envsubst > expanded.yaml
- Create the configmap object:
kubectl create configmap aerospike-conf -n $NAMESPACE --from-file=configs/
- Deploy:
kubectl create -f expanded.yaml
Helm chart for the same can be found here
- Kubernetes 1.8+
- Kubernetes DNS add-in