> 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/guides-and-examples/running-instances/using-helm-charts.md).

# Using Helm charts

How to use Helm charts with your Release instances

### Using Helm charts on your instances

Helm is a package manager for Kubernetes. Helm charts are used to describe related collections of Kubernetes resources. You can use [Helm with Release](/reference-documentation/helm.md).

You can configure Helm by adding a `values.yaml` file to your project repository. As an example, you can see our [Helm Ingress](https://github.com/releasehub-com/helm-ingress) repository on GitHub, which configures a Helm chart for generating an ingress for your application.

### Viewing the instances deployed by Helm

One Helm chart might deploy several instances. You can see these in the same way that you view other instances in an environment. Visit your environment and scroll down on the "Details" page to see all your running instances, including those deployed by Helm.

### Viewing Helm charts directly on your Release cluster

If you want to view the Helm charts that are deployed to your Release cluster, download and configure [Kubectl](https://kubernetes.io/docs/reference/kubectl/kubectl/) on your local machine. This will give you access to the `helm` command, which you can use to see your deployed charts, for example:

```bash
helm list
```

and

```bash
helm get all jenkins -n jenkins
```

### Injecting Release environment variables into your Helm charts

You can inject any environment variables defined in your Release configuration into your Helm `values.yaml` file. Here's an example:

```yaml
web:
  image:
    repository: ${RELEASE_REGISTRY_PATH}
    name: web@sha256
    tag: ${WEB_REGISTRY_IMAGE_SHA}
  hostname: ${WEB_INGRESS_HOST}
  url: "jdbc:postgresql://${WEB_RDS_DB_POOL_HOST}:5432/web"
```

For more information, take a look at the [reference documentation for Helm](/reference-documentation/helm/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/guides-and-examples/running-instances/using-helm-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.