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