Elasticsearch on Container
Was this helpful?
This article provides step-by-step instructions for installing and configuring Elasticsearch within a container-based environment using Helm. This setup is designed to work alongside the OvalEdge application.
Ensure the following before proceeding:
The OvalEdge application must already be deployed.
Write access to the namespace where OvalEdge is deployed.
Helm must be installed and properly configured.
ES-Service.yaml S3 link: https://ovaledge.s3.us-west-1.amazonaws.com/Elasticsearch/es-service.yaml
ES-Deployment.yaml S3 link: https://ovaledge.s3.us-west-1.amazonaws.com/Elasticsearch/es-deployment.yaml
Place the downloaded es-deployment.yaml and es-service.yaml files into the templates directory of your existing Helm chart used for OvalEdge deployment.

Update the values.yaml file to include the required Elasticsearch configuration values (resource limits, environment variables, volume mounts, etc.).
Execute the Helm command to deploy Elasticsearch using the updated Helm chart:
👉Replace <namespace> with the actual namespace where OvalEdge is deployed.
Verify that Elasticsearch is successfully deployed and accessible from the OvalEdge app pod by running a curl request to the health check endpoint:
👉 Replace <dns_or_ip> with the actual DNS name or IP address of the deployment environment.
Ensure that all required ports are open and accessible.
Validate pod status:
For troubleshooting, check logs:
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Was this helpful?
Was this helpful?
helm upgrade --install ovedge-app ./your-helm-chart-directory --namespace <namespace>curl http://<dns_or_ip>:9200/health/es/statuskubectl get pods -n <namespace>kubectl logs <es-pod-name> -n <namespace>
