> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/reference-documentation/helm/open-source-charts.md).

# Open-source charts

You can use open-source Helm charts in your application. At deployment time, Release will add the Helm repository and install its dependencies.

Here's an example showing how you can define an application that will use both Elasticsearch and Vault open-source Helm charts:

```
charts:
- name: elasticsearch
  add: elastic
  install: elastic/elasticsearch
  repo_url: https://helm.elastic.co
  directory: helm/elasticsearch
  values: 
  - values.yaml
- name: vault
  repo_url: https://helm.releases.hashicorp.com
  add: hashicorp
  install: hashicorp/vault
  directory: helm/hashicorp
  values: 
  - values.yml
```

Release will use the values files located in your source control repository. By default, Release will look for the values files in the root of the repository, but you can define a `directory` where the values files are located in your source control repository.

Once you've configured the charts, you can use them in a workflow. Workflows allow you to run the Helm charts in parallel and orchestrate the deployment of all your services.

Here's an example workflow that deploys Elasticsearch and Vault in parallel:

```
workflows:
- name: setup
  parallelize:
  - step: opensource-backend
    tasks:
    - charts.elasticsearch
    - charts.vault
- name: patch
  parallelize:
  - step: opensource-backend
    tasks:
    - charts.elasticsearch
    - charts.vault
```

For more details on how to expose your open-source service to the internet, see our guide to [Helm ingress and networking](https://github.com/releasehub-com/docs/blob/main/reference-guide/ingress-and-networking.md). For more information on configuring Helm charts, values files, or passing environment variables to your Helm chart, see [Helm configuration](https://github.com/releasehub-com/docs/blob/main/reference-guide/configuration.md).


---

# 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.release.com/reference-documentation/helm/open-source-charts.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.