Skip to main content
We are excited to be a part of AWS re:Invent 2024. Visit us at booth #1844 in Las Vegas.More info
Loading
Version: Operator 3.1.0

Use the Aerospike Kubernetes Operator to Modify an Aerospike Cluster

The Aerospike Kubernetes Operator makes it easier for you to use Aerospike Enterprise clusters on Kubernetes. Instead of making changes to the cluster by hand, you specify changes in the Aerospike cluster CR file, then use kubectl apply to apply these changes.

For this example assume that the cluster was deployed using a file named aerospike-cluster.yaml.

Example Configuration Change​

Change the spec.aerospikeConfig.service.proto-fd-max field in the aerocluster CR to 20000

apiVersion: asdb.aerospike.com/v1
kind: AerospikeCluster
metadata:
  name: aerocluster
  namespace: aerospike
spec:
  size: 2
  image: aerospike/aerospike-server-enterprise:6.4.0.0
  aerospikeConfig:
    service:
      proto-fd-max: 15000
  .
  .

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

kubectl apply -f aerospike-cluster.yaml

Check the Pods​

Pods will undergo a rolling restart.

Output:

$ kubectl get pods -n aerospike
NAME          READY   STATUS              RESTARTS   AGE
aerocluster-0-0     1/1     Running         0          3m6s
aerocluster-0-1     1/1     Running         0          3m6s
aerocluster-0-2     1/1     Running         0          30s
aerocluster-0-3     1/1     Terminating     0          30s

After all the pods have restarted, use kubectl describe to get status of the cluster.

Check spec.aerospikeConfig.service.proto-fd-max in status.

$ kubectl -n aerospike describe aerospikecluster aerocluster
Name:         aerocluster
Namespace:    aerospike
Kind:         AerospikeCluster
.
.
Status:
  Aerospike Config:
    Service:
      Proto - Fd - Max:   20000
  .
  .

Unchangeable Parameters​

replication-factor and strong-consistency cannot be changed using the Aerospike cluster CR file. These parameters are set the first time the pods start and must remain the same afterward. However, you can create new pods by starting a new rack with the updated parameter value. See Scaling Namespace Storage for Aerospike on Kubernetes for more information.

Last updated on