Skip to main content
Version: Operator 2.0.0

Install the Operator from OperatorHub

This procedure applies to:

Install the Operator Lifecycle Manager (OLM)

Install OLM on your Kubernetes cluster with the command:

curl -sL | bash -s v0.20.0

Install the Aerospike Kubernetes Operator

kubectl create -f

Verify the Operator is Running

Verify that the Operator's CSV is in the Succeeded phase.

$ kubectl get csv -n operators aerospike-kubernetes-operator.v2.0.0

You will see output similar to the following:

NAME                                   DISPLAY                         VERSION   REPLACES   PHASE
aerospike-kubernetes-operator.v2.0.0 Aerospike Kubernetes Operator 2.0.0 Succeeded

Check Operator Logs

The Operator runs as two replicas by default, for higher availability. Run the following command to follow the logs for the Operator pods.

kubectl -n operators logs -f deployment/aerospike-operator-controller-manager manager

Sample output:

2022-01-15T19:09:58.058Z    INFO    controller-runtime.metrics  metrics server is starting to listen    {"addr": ""}
2022-01-15T19:09:58.062Z INFO setup Init aerospike-server config schemas

2022-01-15T19:09:58.071Z DEBUG schema-map Config schema added {"version": "4.7.0"}
2022-01-15T19:09:58.072Z INFO aerospikecluster-resource Registering mutating webhook to the webhook server
2022-01-15T19:09:58.073Z INFO controller-runtime.webhook registering webhook {"path": "/mutate-asdb-aerospike-com-v1beta1-aerospikecluster"}
2022-01-15T19:09:58.073Z INFO controller-runtime.builder skip registering a mutating webhook, admission.Defaulter interface is not implemented {"GVK": ", Kind=AerospikeCluster"}
2022-01-15T19:09:58.073Z INFO controller-runtime.builder Registering a validating webhook {"GVK": ", Kind=AerospikeCluster", "path": "/validate-asdb-aerospike-com-v1beta1-aerospikecluster"}
2022-01-15T19:09:58.073Z INFO controller-runtime.webhook registering webhook {"path": "/validate-asdb-aerospike-com-v1beta1-aerospikecluster"}
2022-01-15T19:09:58.074Z INFO setup Starting manager
I1015 19:09:58.074722 1 leaderelection.go:243] attempting to acquire leader lease aerospike/

Grant permissions to the target namespaces

The Operator is installed in the operators namespace and needs additional service accounts configured for the Kubernetes namespaces the Aerospike clusters will be created in.

The procedure to use the namespace aerospike is as follows:

Create the namespace

Create the Kubernetes namespace if not already created:

kubectl create namespace aerospike

Create a service account

kubectl -n aerospike create  serviceaccount aerospike-operator-controller-manager

Update the operator's ClusterRoleBinding

Next, add this service account to the Operator's ClusterRoleBinding. To do this, run the following command:

kubectl edit $(kubectl get  | grep aerospike-kubernetes-operator | grep -v -- "-opera-" | cut -f 1 -d " ")

This command launches an editor. Append the following lines to the subjects section:

  # A new entry for aerospike.
# Replace aerospike with your namespace
- kind: ServiceAccount
name: aerospike-operator-controller-manager
namespace: aerospike

Save and ensure that the changes are applied.

Here is a full example of the Operator's ClusterRoleBinding targeting the aerospike namespace.

kind: ClusterRoleBinding
creationTimestamp: "2022-01-16T10:48:36Z"
olm.owner: aerospike-kubernetes-operator.v2.1.0
olm.owner.kind: ClusterServiceVersion
olm.owner.namespace: test ""
name: aerospike-kubernetes-operator.v2.1.0-74b946466d
resourceVersion: "51841234"
uid: be546dd5-b21e-4cc3-8a07-e2fe5fe5274c
kind: ClusterRole
name: aerospike-kubernetes-operator.v2.1.0-74b946466d
- kind: ServiceAccount
name: aerospike-operator-controller-manager
namespace: operators

# New entry
- kind: ServiceAccount
name: aerospike-operator-controller-manager
namespace: aerospike