spec VS helmfile

There was recently score.dev, but that is also just used by one tool.

Yesterday I was thinking about the roadmap and the discussions that are happening in the community (you can check them here and feel free to open one or contribute to an active one) and I am excited to see how much we have to look forward in 2023.

A month ago we open sourced Score. The community response has been really great so far (just over 1k stars in 4 weeks) and we got many questions thrown at us:

Hi all, I am Giulia, Community Manager and part of the team that launched Score.dev a week ago. My team and I believe that developers shouldn’t fight with tooling and advocate for a workload-centric approach to development. We’re on a mission to reduce cognitive load on developers, minimize configuration drift and mismanagement, and improve the developer experience. Want to join us as a contributor? Read the official announcement to learn more. Or check us out on GitHub!

Last week we released score-spec and I asked a few communities for feedback on how you manage configuration between multiple environments and a lot of you (thanks!) came up with some answers and more questions. Here I wanted to list the pros and cons, in my humble opinion, of the top approaches suggested. Feel free to add yours as well!

sudo wget https://github.com/helmfile/helmfile/releases/download/v0.159.0/helmfile_0.159.0_linux_amd64.tar.gz sudo tar -xxf helmfile_0.159.0_linux_amd64.tar.gz sudo rm helmfile_0.159.0_linux_amd64.tar.gz sudo mv helmfile /usr/local/bin/

Installation: https://github.com/helmfile/helmfile/releases

What are the benefits over using helmfile? https://helmfile.readthedocs.io/

Helm charts and Helmfile

And now I can just run dudo -l "https://github.com/helmfile/helmfile/releases/download/v{{ version }}/helmfile_{{ version }}_{{ os }}_{{ arch }}.tar.gz" -i /tmp/helmfile.tar.gz -p $HELMFILE_VERSION

I might be misunderstanding your question but we use https://github.com/helmfile/helmfile along with Argo, so essentially between eks and those I could rebuild our entire cluster in minutes.

I am asking which do you choose, Flux or Helmfile. edit: and what criteria do you use to select.

do you publish your own helm chart for your internal services and use it in every environment? if so, you could try to use helmfile within the service's repo itself and store values in a helm/$env directory. then enhance your ci to deploy to dev after the merge/image build phase directly. to try and cut out what sounds like a "deployment/config repo" step you have in the middle that's making everything a pain.

I've used helmfile before to declaratively manage multiple helm charts. It's a higher-level tool, and still uses helm under the hood.