Elasticsearch
🎬 Watch Before You Begin
🧠Video Timeline
In this video, you’ll see how to configure Docker credentials, generate certificates, and install Elasticsearch using Helm.
-
[02:30]
Configure Docker credentials to allow downloading custom Docker images.
-
[03:36]
Visit site docker.com and fetch these values - user id, email and create a new personal access token.
-
[04:50]
Validate docker credentials are accurate (look for Login Succeeded).
Create kubernetes secrets to store the docker credentials.
-
[05:30]
Generate custom certificates to go with the Elasticsearch install.
This will take 2 minutes or so as we download docker image to generate certificates.
-
[07:00]
Install Elasticsearch.
See the installation via Headlamp dashboard.
-
[11:42]
Video ends
🧠Video Timeline
In this video, you’ll see how to configure Docker credentials, generate certificates, and install Elasticsearch using Helm.
-
[02:30]
Configure Docker credentials to allow downloading custom Docker images. -
[03:36]
Visit site docker.com and fetch these values - user id, email and create a new personal access token. -
[04:50]
Validate docker credentials are accurate (look for Login Succeeded). Create kubernetes secrets to store the docker credentials. -
[05:30]
Generate custom certificates to go with the Elasticsearch install. This will take 2 minutes or so as we download docker image to generate certificates. -
[07:00]
Install Elasticsearch. See the installation via Headlamp dashboard. -
[11:42]
Video ends
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.
###CAUTION: Look for
Replace the username, password (token) and email as mentioned.
export UNAMESPACE={{UNAMESPACE}}
# replace user id, email, token appropriately
DOCKER_USER_ID=put-your-value-here-docker-id-example-hjrc
DOCKER_USER_EMAIL=put-your-value-here-example-user-at-gmail.com
DOCKER_USER_TOKEN=put-your-value-here-keep-it-secret
# let's also test if it is valid. you should see confirmation 'Login Succeeded'
echo $DOCKER_USER_TOKEN | docker login --username "$DOCKER_USER_ID" --password-stdin
kubectl create secret docker-registry registry-camunda-cloud \
--namespace={{UNAMESPACE}} \
--docker-server=registry.camunda.cloud \
--docker-username=${DOCKER_USER_ID} \
--docker-password=${DOCKER_USER_TOKEN} \
--docker-email=${DOCKER_USER_EMAIL}
kubectl create secret docker-registry registry-docker-hub \
--namespace={{UNAMESPACE}} \
--docker-server=hub.docker.com \
--docker-username=${DOCKER_USER_ID} \
--docker-password=${DOCKER_USER_TOKEN} \
--docker-email=${DOCKER_USER_EMAIL}
###CAUTION: Look for
Login Succeeded confirmation after running the docker login command. If you see any error, please check the values and try again.
Install elastic components - elk certs
Important: Make sure Docker CLI command is supported on the terminal window.
# 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 CLI command is supported on the terminal window.
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 Elasticsearch
# 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-ap-21.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.
Post Command-Set Execution: Click to view screen shot - Elasticsearch pod up and running.
Click on image to enlarge