github-action-helm3 VS Zenko

So, I am using Github actions and helmfile to setup a workflow that allows us to deploy resources to our clusters. All the code is in one repo with the below structure. The problem is that there really is not a very good plugin to deploy multiple helm charts into S3 and GitHub pages is public. The only public forGitHub actions to s3 only works for one repository at a time and I want a situation where CI/CD "loops" through the charts in the charts folder and finds the one with a change and requires that they value in the `chart.yaml` file be bumped up. How can I achieve this?

> Iteration speed and blazing fast automated tests.

Wholeheartedly agreed!

It is also nice to have that additional assurance of being able to self-host things (if ever necessary) and not being locked into a singular implementation. For example, that's why managed database offerings generally aren't that risky to use, given that they're built on already established projects (e.g. compatible with MySQL/MariaDB/PostgreSQL).

> When I discovered minio, I suddenly got much more confident coding against s3.

MinIO is pretty good, but licensing wise could become problematic if you don't work on something open source but ever want to run it in prod. Not really what this discussion is about, but AGPL is worth mentioning: https://github.com/minio/minio/blob/master/LICENSE

That said, thankfully S3 is so common that we have alternatives even to MinIO available, like Zenko https://www.zenko.io/ and Garage https://garagehq.deuxfleurs.fr/ both of which are good for both local development as well as hosting in whatever environments necessary.

Have you seen https://www.zenko.io already? Would that be something that could work for you? It‘s more or less an additional layer with s3 support for existing infrastructure.

Well, technically with a bit of work you can use anything self-hosted that is S3 compatible.

Personally, I rather like:

  - https://www.zenko.io/

Have you seen this project: https://github.com/scality/Zenko