@lvca I never used helm charts, so I don't think I can be of help here (at least in the short run). Sorry.

Great works, thanks.
Now, let me think about creating a separate "arcadedb-helm-chart" repository or keep this contribution in the main repository.

The dedicated repo approach works particularly well because:

• Database code and deployment configuration have different lifecycles
• It's easier for users to find deployment options in a dedicated repo
• It allows for independent versioning of deployment configurations

Let me think a bit about the better way to manage this.

BTW, a great and valuable work, thank you!

After some consultation, the PR will be merged here, instead of creating a new, dedicated repo

Just a small request: can you add a readme.md with some basic instructions on how to use it?

moreover, What should we do on relases? Just upgrade the version inside the files?

Yes, I'll add a README in a bit.
For versioning, I'd just worry about this file here: k8s/helm/Chart.yaml
The generated docs from helm do a decent job of explaining the two version settings I think.

Added a README in 631367e by using Bitnami's helm readme generator: https://github.com/bitnami/readme-generator-for-helm

If you like, and time opens up for me I can probably add that as a step to the helm test perhaps, install that doc generator and run it using the values.yaml file to ensure any changes are documented and README is updated.

Aside from that, could also do a minikube step to install the chart using default values and just make sure some pods/svc end up happy. But again, I'm a bit slim for time these days but can probably swing it to be work related to a certain extent. :)

a dedicated workflow to test helm with minikube and also the doc would be amazing.
If you don't have time right now, we can start to merge this pr and then do the additional work on a new one
I'm not a big fan of long-standing prs.

Let me know when I can merge, thanks

I'm not a big fan of long-standing prs.

I think we're aligned here :) As mentioned we're intending to use this for a PoC project so will be sure to upstream anything we see during our use. Thanks, ready to merge from my end.

Thanks @milesgranger! @gramian the readme.md provided by @milesgranger should be also in our docs. WDYT?

I suggest to add a section, as for Docker and plain K8s, to the docs with some basic info about helm and a reference to this chart. I would rather not add the parameters as this is very specific to this very chart, and rather refer to the README instead.
As for the compose file, somebody seriously using a helm chart to deploy ArcadeDB will write their own adapted version (probably based on this) but understand the parameters. I would think the benefit of having this is to provide a good template to start of from which happens to work unmodified on its own, too, right?

Also from me, thanks @milesgranger !

BTW: I guess, the liveness probe should not be the ready endpoint, but likely user specific ie a SELECT 'alive'; query to a relevant database?