Just set this up recently. I’m using chartmuseum as a chart repository. If I run ‘helm search charmuseum/$chart_name’, I’ll get the chart and version number. From there you just need a bash script that runs when you re deploy your chart. The script should: • bump the version patch by one (using the output of the search command), • use sed to replace the version in chart.yaml, • package the chart with that version, • put the package in chart museum, • and deploy More on reddit.com

Been awhile since I touched Elastic stuff (though I used to work there). As of a few years back there was a big push for their ECK operator (Elastic Cloud on Kubernetes). Pretty sure it’s still active. Here’s the repo and helm instructions from their docs: Repo: https://github.com/elastic/cloud-on-k8s Helm source: https://github.com/elastic/cloud-on-k8s/tree/main/deploy Installation: https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-install-helm.html 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