Elastic
Runs as a persistent data store for the Camunda platform.
It is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases.
Edit this block in text editor before running the same.
Replace the username, password (token) and email as mentioned.
Replace the username, password (token) and email as mentioned.
# replace user id, email, token appropriately
kubectl create secret docker-registry registry-camunda-cloud \
--namespace=$UNAMESPACE \
--docker-server=registry.camunda.cloud \
--docker-username=your-docker-account-uid \
--docker-password=your-docker-account-token \
--docker-email=your-docker-account-email
# replace user id, email, token appropriately
kubectl create secret docker-registry registry-docker-hub \
--namespace=$UNAMESPACE \
--docker-server=hub.docker.com \
--docker-username=your-docker-account-uid \
--docker-password=your-docker-account-token \
--docker-email=your-docker-account-email
Install elastic components - elk certs
Important: Make sure Docker Desktop app is running on your local machine.
# Config => secret/elastic-certificates created
# Config => secret/elasticsearch-master-certs created
# Config => secret/elastic-jks created
###CAUTION: You may have to run the script twice. Sometimes the certs are not created on first run. Please check and proceed.
Important: Make sure Docker Desktop app is running on your local machine.
UNAMESPACE=$UNAMESPACE envsubst < elk-makefile | sh
After this, you should see secrets created in your namespace (via Project Lens UI app).
# Config => secret/elastic-certificates created
# Config => secret/elasticsearch-master-certs created
# Config => secret/elastic-jks created
###CAUTION: You may have to run the script twice. Sometimes the certs are not created on first run. Please check and proceed.
Install elastic
# It may take about 3 to 5 minutes for the pod to be in running state.
helm repo add elastic https://helm.elastic.co
helm repo update
helm install elasticsearch elastic/elasticsearch -n $UNAMESPACE -f elasticsearch.yaml
After this, you should see Elastic pod running.
# It may take about 3 to 5 minutes for the pod to be in running state.