I've never done that specifically, but I have used envsubst to set values in files. More on reddit.com

Using branches to segregate environments is a very bad option. I cannot recommend enough this video https://youtu.be/CvMevMHExHk?si=eumCCpgnBixLMn1O More on reddit.com

If you push and pull helm charts/images from ECR, you need to make sure that the runner has correct permissions. To do that, you need to create an IRSA role with necessary permissions attached. This is on AWS side. On K8s side you need to attach arn of the role created as an annotation (you’ll find somewhere in docs). In general, CD of Helm Chart is usually 1:1 when compared to image deployment and can be viewed as an extension of image build pipeline. However, the more clusters you have, the less I like it and favor FluxCD, especially in this case as it has insane GitHub/GitLab features. On of the ways to change image version would be to store it after image build/push in GitLab env variable, pass it to helm task, where something similar to helm upgrade —install -n —set image.tag=. Obviously the set flag will differ, depending on structure of your values file. More on reddit.com

I created a dependency management tool named Updatecli. It's a command line tool that we run either from our machine or from the CI environment. You define in a manifest how a file from a git repository, should be updated and then each time Updatecli is executed, it updates the repository if needed. We use it on many project such as Jenkins to keep any yaml file lie helm chart, helmfile, dockerfile, etc. You can have an overview on: https://www.updatecli.io/docs/guides/helm-chart/ and a real life scenario on https://github.com/jenkins-infra/helm-charts/tree/main https://github.com/rancherlabs/updatecli-automation/tree/main Feel free to reach out if you have any questions More on reddit.com