I'll take this.

@RanadeepPolavarapu That will be great.

I guess I don't have much input on this task as I don't have too much experience with creating helm charts.

I guess it will be a good practice to follow our general guidelines of keeping things as lean, well documented and as standard as possible.

@RanadeepPolavarapu Do you think we need to add the chart in this repo or do you want me to open a new repo just for it (appwrite/helm-chart), what is more common across other projects maintaining a helm chart?

Should we aim to create the helm chart with production ready settings or maybe we create multiple versions available? Is there any convention for replacing or choosing ENV settings?

Do you think we need to add the chart in this repo or do you want me to open a new repo just for it (appwrite/helm-chart), what is more common across other projects maintaining a helm chart?

Just create the chart in this repository, it's redundant to manage it within another repository.

Should we aim to create the helm chart with production ready settings or maybe we create multiple versions available? Is there any convention for replacing or choosing ENV settings?

The default values.yaml should describe production ready settings. Since you're publishing/providing the AppWrite application/helm charts, I wouldn't recommend including a values.dev.yaml within the same VCS as the helm chart being provided. This is something that should be created within a deployment repository that end users of appwrite shouldn't be able to see..

OK great! if you need any help feel free to contact me, we can also chat on Gitter.

Is it still open ? @eldadfux

Going to work on this week.

มันทำงานยังไง

คราบ

@CQ10 please use english.

It's been 15 days since the last response. If no one is working on it, I'd like to take this up.

@mbtamuli yeh I guess you can work on it. It's been 26 days with no updates.

You can reach me out on our Discord channel, feel free to ask me anything.

https://discord.gg/JbdEMd4

@mbtamuli If you need any assist in implementing the helm chart I will be happy to help :D

@mbtamuli please keep us updated on what is going on with this issue. While this is assigned, other people who want to help with it don't get the chance.

Any updates on this? If no updates happens during this week I might take over it so I can work it by the next weekend :D

Sorry people, I got busy and haven't been able to work on this. Feel free to take it up. @mostafahussein

@mbtamuli thanks for giving it a try! @mostafahussein - as always feel free to reach out for any question.

@mostafahussein do you think we can use this tool to convert our docker-compose.yml to a helm chart? maybe we can even use it to automate the process whenever we release a new tag...

Do you mean Kompose or something else?

ดีคราบ

@mostafahussein yeah, sorry - forgot to paste the link:
https://kompose.io/installation/

I would like to volunteer for that. I have questions:
Do we want to include the database? managing a MariaDb in Kubernetes to a production level grade is not as easy.
Helm is not anymore the only way of deploying stacks on kubernetes. Operator is the new way to go. What do you think?

@nicolasgere We can always allow to customise the configuration for a managed DB or any 3rd party solution. I thinks it's OK to start with the current Appwrite+MariaDB image we use as a starting point.

Haven't heard about Operator, can you share a link?

https://coreos.com/operators/
https://kubernetes.io/docs/concepts/extend-kubernetes/operator/

@eldadfux Operator pattern is the way to go for stateful clusters. Its basically a controller for your app that uses kubernetes api.

Anyway, I think that it doesn't replace helm. Helm would be useful anyway.

@javib51 I think it will be best if you create a new issue for the operator controller and i'll assign it to you.

@mostafahussein do you think you'll be able to work on the helm chart anytime soon or @javib51 can take this one too?

@eldadfux Sure! We can organize it from there. I'm a bit busy this week but I would find some time to work on it.

So you don't need help at the end right?

@nicolasgere Not for now, but I will ping you on the new issue if I need it. Thanks for asking!