clear-text

Aerospike JMS Outbound clear text example

This example deploys Aerospike JMS Outbound connectors and an Aerospike cluster without TLS configured.

Prerequisites

• Kubernetes cluster
• Helm v3
• A JMS cluster with brokers reachable from the pods in the Kubernetes cluster
• An Aerospike cluster that can connect to Pods in the Kubernetes cluster The Aerospike cluster can be deployed in the same Kubernetes cluster using Aerospike Kubernetes Operator
• Aerospike JMS Connector Helm chart

Clone this repository.

• A clone of this git repository

Deploy connectors.

All subsequent commands are run from this directory.

Create a new Kubernetes namespace

Create a Kubernetes namespace if not already done

kubectl create namespace aerospike

Deploy the connectors.

Update the as-jms-outbound-values.yaml file to change JMS connector configuration to point to backend JMS provider.

Deploy the connectors using configuration from as-jms-outbound-values.yaml

helm install --namespace aerospike as-jms-outbound -f as-jms-outbound-values.yaml aerospike/aerospike-jms-outbound

Deploy the Aerospike cluster

If you do not have a preexisting Aerospike server, install Aerospike Kubernetes Operator. The steps below will deploy an Aerospike cluster using Aerospike Kubernetes Operator and this sample custom resource.

Create secrets

Create the secret for aerospike using your Aerospike licence file

kubectl -n aerospike create secret generic aerospike-secret --from-file=<path to features.conf>

Launch the Aerospike cluster

kubectl -n aerospike create -f aerospike.yaml 

Write data to Aerospike

You can write data to Aerospike using aql, asbench tools or using your own code. The record updates should show up in your JMS provider queue/topic.

Cleanup

Remove the Aerospike cluster

kubectl -n aerospike delete -f aerospike.yaml 

Remove the connectors

helm -n aerospike uninstall as-jms-outbound

Delete the secrets

kubectl -n aerospike delete secrets aerospike-secret