- Ordering of Helm subcharts
Re: Ordering of Helm subcharts
Paul Czarkowski <pczarkowski@...>
toggle quoted messageShow quoted text
I could see two options:
* use the `post-install` hook for the pipeline-run ?
* use two helm charts, one for the tasks and pipeline, the other for the pipeline-run. the latter can have the former as a dependency, or you could use helmfile or similar to order them.
According to the documentation
here it is possible to declare dependencies
in Heln charts using the charts subdirectory. However, the order in which the
K8s resources will be deployed depends on the implementation of
Here only native K8s resources will be taken into account.
Now I've got a Helm chart dependency with no native K8s resources at all.
Instead only Tekton pipeline resources are used which obviously (after several
attempts) makes the order of the deployed Tekton resources unpredictable.
Actually I want to have these Tekton resources deployed:
- first: Tekton task
- second: Tekton pipeline
- third: Tekton pipeline-run
And I have created this chart structure to achieve it (of course with all the
necessary files in place):
As mentioned the order is not predictable and mostly the pipeline run is started
before the tasks are available which leads to an error.
Now I'm not sure if this is worth a feature request which says to include not
only native K8s resources but instead all resources available inside the
I'd like to hear some opinions. Thanks!
Join email@example.com to automatically receive all group messages.