Create Helm charts for deployment to any Kubernetes cluster for scalability

[jeffzhu503]

One of features in Artipie is "It is horizontally scalable, you can add servers easily".
We are using docker to deploy Artipie. So how can we deploy more dockers to make it scalable? My suggestion is we will need to create Helm chart how we deploy Artipie and make use of Kubernetes features in our project. This will also help us promote the project to Kubernetes community.

[0crat]

@g4s8/z, @olenagerasimova/z please, pay attention to this issue

[g4s8]

@jeffzhu503 agree, Helm chart for Artipie sounds good.

[jeffzhu503]

docker-composer for Artipie central is a good start. But we need to create Helm chart with templates and values to support the deployment to any Kubernetes cluster.

[cambierr]

I actually did it for our "corporate" deployment. I could easily do some changes to it to be able to share it... would a repository be available to open a PR to ?

[Sammers21]

@cambierr, yes, feel free to submit a pull request.

[cambierr]

to this repo ? something like /helm/charts/Chart.yaml & co

[g4s8]

@cambierr thanks for your intention, can you please suggest how other projects usually do that? We're not really familiar with charts writing. If chart has a lot of files and it has different versioning flow (it doesn't related to Artipie version) we can create another repo. If chart should be released at the same time as Artipie, I think it should be placed in same repo.

[cambierr]

Well, it all depends of the project repository philosophy (mono repo vs multi repo).

Given Artipie's one, I'd suggest a dedicated repository (as done by Rancher with https://github.com/rancher/helm3-charts to quote anoter project using the multi-repo principle).

I'd thus suggest a dedicated "helm" repository to be able to push those and manage them independently from the main application since charts can have a different life cycle.

[g4s8]

@cambierr got it, thanks. I created https://github.com/artipie/helm-charts repository and moved this ticket here.

[g4s8]

@jeffzhu503 see #2