-
Type: Task
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Jenkins X
-
Environment:nuxeo-helm-chart 1.0.5
-
Tags:
Context
According to documentation: https://v2.helm.sh/docs/developing_charts/#tags-and-condition-fields-in-requirements-yaml
For multiple level dependencies the condition is prependend by the path to the parent chart.
But this wasn't the case in Helm 2.14, the prepend wasn't done, see https://github.com/helm/helm/pull/4783 (fixed in 2.15).
As it, when we use nuxeo helm chart in a preview chart, the following in values.yaml works in helm 2.14 but not in helm 2.15 and higher.
nuxeo:
elasticsearch:
deploy: true
The condition is currently:
condition: nuxeo.elasticsearch.deploy
Thus, with helm 2.15, the values is expected to be:
nuxeo:
nuxeo:
elasticsearch:
deploy: true
Jenkins X builder ships helm 2.14 whereas we have helm 2.16 on our local computer.
This is error-prone when it comes to debug a chart on our computer, we should update our chart to be compatible with helm 2.16.
Request
We want to update the helm version in our builders if it is possible (because helm come from jx-base, reference).
Furthermore, as we can set several conditions in requirements.yml, we can set the condition working with helm 2.16 and then the one for helm 2.14.
Which should lead to:
condition: elasticsearch.deploy,nuxeo.elasticsearch.deploy
This will handle every cases, advocating helm 2.16 and the following values for a dependant chart:
nuxeo:
elasticsearch:
deploy: true
When using nuxeo chart directly, the following values should be used:
nuxeo:
something: ...
...
elasticsearch:
deploy: true