Skip to content

Latest commit

 

History

History

clear-text

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
README.md
README.md
 
 
aerospike.yaml
aerospike.yaml
 
 
as-jms-inbound-values.yaml
as-jms-inbound-values.yaml
 
 

README.md

Aerospike JMS Inbound clear text example

This example deploys Aerospike JMS Inbound 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 reachable from the connectors 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 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

Deploy the connectors.

Update the as-jms-inbound-values.yaml file to change connectorConfig.jms to consume messages from JMS cluster with broker and update connectorConfig.aerospike section to point to your destination Aerospike cluster. Deploy the connectors using configuration from as-jms-inbound-values.yaml

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

Write data to Aerospike

You can write data into JMS queue or topic using tools/clients of your choice. An Aerospike record corresponding to each message should show up in your Aerospike database.

Cleanup

Remove the Aerospike cluster

kubectl -n aerospike delete -f aerospike.yaml

Remove the connectors

helm -n aerospike uninstall as-jms-inbound

Delete the secrets

kubectl -n aerospike delete secrets aerospike-secret