helmfile | Deploy Kubernetes Helm Charts

I have helmfile

I tried to pass value to helmfile with --set

I want to deploy IBM-MQ to Kubernetes (Rancher) using helmfile. I've found this link and did everything as described in the guide: https://artifacthub.io/packages/helm/ibm-charts/ibm-mqadvanced-server-dev.

But the pod is not starting with the error: "ImagePullBackOff". What could be the problem? My helmfile:

Say you need to deploy a public helm chart (like jenkins/jenkins) with a lot of values. I want to write those values over multiple files and also use go templates inside those values files. I then want to compose them together and deploy them. Is there a way to write a meta - level helm chart that creates the values as a manifest then installs a sub chart based on those values?

I’m aware of kustomize, helmfile, and sub charts. I guess none of them just feel like the thing I want (or maybe I’m not using them properly). Kustomize doesn’t support go templates. Helmfile is good for composing and selecting values but not necessarily templating those values files (or maybe it does). Let me know if I’m asking a duplicate.

I have one question regarding helmfile. The question is: how to set annotations to deployment using helmfile? I've tried by using set instruction but It's not working. Also didn't find any information in docs.

What may be causing make fail every other time (and thus succeed every other time) in the below case?

Reduced Makefile:

I have a helmfile release with multiple charts. There are values.yaml inside each chart. Рow to make values inside those values.yaml ​​change depending on environment? I know how to parameterize helmfile's values.yaml, but I can't find any way to throw those values further into the charts values.yaml. Can someone help me with that?

I have created a Node application for which I want to automate the deployment. Up till now I only automated the building process, i.e. install dependencies, create the docker image and push to the Azure Container Registry. This works perfectly fine and corresponds to the code below which is not commented away. In the current process I still need to

1. manually change the image tag in my helmfile configuration and
2. manually perform a helmfile -environment= sync.

My struggle is in the second part, for I believe the first part is easily implemented when I have a setup for the second.

In the source directory of the repository I have the helmfile.yaml which could be called immediately after the build. This is what I tried to achieve with the below setup which is commented. My thoughts were to have a container on which helfmile is already installed, e.g. cablespaghetti/helmfile-docker, then connect to the K8s cluster using the Azure kubectl task to do so, followed by executing the helmfile sync command. This approach failed as I got a Docker exec fail with exit code 1, probably because the specified container uses the ENTRYPOINT approach, which is not allowed in the Azure Pipeline.

The approach however feels somewhat cumbersome, as if I am missing a much simpler approach to 'simply' perform a helmfile sync command. How can I get this to work?

I'm using helmfile to install my Helm chart and other dependencies charts. I want to use templated values in the value files.
From this resolved issue, it looks like templating in value files is supported. However, I tested with the following files: helmfile.yaml: