> 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.md).

# Helm

Release supports Helm 3 charts, so you can mix Docker Compose-style services with Helm-based services.

If you use Helm for your in-house services, Release allows you to define builds that can be referenced from your values files. Release also provides environment variables for the generated hostnames and ingress in your Helm charts to get your application on the internet.

We recommend Helm if you use Release with many microservices. Helm allows you to define all resources and gives you additional control of Kubernetes resources for your microservices.

You can deploy both open-source charts from Helm repositories and charts from your source control system.

Release uses the Helm chart definition to orchestrate the deployment of your application.

Here is a simple example of how to define a Helm chart for your application:

```
charts:
- name: elasticsearch
  add: elastic
  repo_url: https://helm.elastic.co
  directory: elasticsearch
  values: values.yaml
- name: acme-app
  directory: helm
  values: 
  - values.yaml
workflows:
- name: setup
  parallelize:
  - step: elasticsearch
    tasks:
    - charts.elasticsearch
  - step: acme-app
    tasks:
    - charts.acme-app
- name: patch
  parallelize:
  - step: acme-app
    tasks:
    - charts.acme-app
```


---

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