> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/deployment-and-maintenance/installation/elasticsearch-on-container.md).

# Elasticsearch on Container

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**.

## Prerequisites

**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.

## Installation Steps

### **Download Deployment Files**

* **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>

### **Integrate Deployment Files into Helm Chart**

* Place the downloaded `es-deployment.yaml` and `es-service.yaml` files into the **templates** directory of your existing Helm chart used for OvalEdge deployment.<br>

  <figure><img src="https://content.gitbook.com/content/8fgltewNgYZ8ucAp7Svt/blobs/D6ZQsXZJfRoDVIwYi5OK/image.png" alt=""><figcaption></figcaption></figure>
* Update the `values.yaml` file to include the required **Elasticsearch configuration values** (resource limits, environment variables, volume mounts, etc.).

### **Deploy Elasticsearch**

* Execute the Helm command to deploy Elasticsearch using the updated Helm chart:

  ```bash
  helm upgrade --install ovedge-app ./your-helm-chart-directory --namespace <namespace>
  ```

  👉Replace `<namespace>` with the actual namespace where OvalEdge is deployed.

### **Verify Deployment**

* Verify that Elasticsearch is successfully deployed and accessible from the OvalEdge app pod by running a curl request to the health check endpoint:

  ```bash
  curl http://<dns_or_ip>:9200/health/es/status
  ```

  👉 Replace `<dns_or_ip>` with the actual DNS name or IP address of the deployment environment.

{% hint style="info" %}

* Ensure that all required ports are open and accessible.
* Validate pod status:

  ```bash
  kubectl get pods -n <namespace>
  ```
* For troubleshooting, check logs:

  ```bash
  kubectl logs <es-pod-name> -n <namespace>
  ```

{% endhint %}

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/deployment-and-maintenance/installation/elasticsearch-on-container.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.