Dependencies between releases?

[jkroepke]

Hi,

it is possible to define dependencies between releases?

For example, I have the cert-manager Chart and an 2nd chart to provide a ClusterIssuer (CRD of cert-manager). The 2nd chart should wait until the cert-manager Chart is installed. Otherwise the 2nd chart would fail.

[reixd]

Hi @jkroepke, I solved this type of dependency like this:

releases:

- name: "cert-manager"
  namespace: "cert-manager"
  chart: "jetstack/cert-manager"
  version: {{ .Values.chart_version | quote }}
  #[...]

- name: 'cert-manager-issuers'
  needs: ['cert-manager/cert-manager']
  chart: "kubernetes-incubator/raw"
  namespace: "cert-manager"
  version: {{ .Values.cert_manager_issuers_chart_version | quote }}
  #[...]

Take a look at the needs keyword. See DAG-aware installation/deletion ordering

[jkroepke]

Great. it should be mention here, too. https://github.com/roboll/helmfile#configuration (I tough, all options are mention here.)

I was looking for "depends" or "dependency", but I found nothing. Thanks.

[jkroepke]

Note: helm diff will fail here on first install:

STDERR:
  Error: Failed to render chart: exit status 1: Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "ClusterIssuer" in version "cert-manager.io/v1"
  Error: plugin "diff" exited with error