Create a Helm Chart for Appwrite about appwrite

[gopalkhasria]

Any updates on this?

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..

[mostafahussein]

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

[k3env]

I created a helm chart repository. Part of the functionality is currently unavailable, like functions.
Part of the functionality, such as traefik, has been replaced with standard kubernetes objects (IngressClass)
Link to repo https://github.com/k3env/appwrite-helm

[eldadfux]

@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

[eldadfux]

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

[nicolasgere]

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

[CQ10]

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

[eldadfux]

@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.

[mostafahussein]

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

[mostafahussein]

Do you mean Kompose or something else?

[nicolasgere]

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?

[javib51]

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.

[eldadfux]

@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?

[javib51]

@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.

[javib51]

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

[StarTrooper08]

Hello,
Can I take on this issue.
But I'll require help by professional.
Can I go for it??

[kodumbeats]

https://github.com/kubernetes/kompose Something like this might be a good idea.

kompose is a tool to help users who are familiar with docker-compose move to Kubernetes. kompose takes a Docker Compose file and translates it into Kubernetes resources.

@loftwah I had a similar idea, but a kompose chart doesn't generate a helm chart ready to customize with a values.yml. This issue has spun off into #364 which might be more appropriate, considering Appwrite's stateful dependencies.

[karstengresch]

Instead of Kompose, move2kube (https://move2kube.konveyor.io/) could make sense. Would love to just give it a try but I'm buried w/ stuff.

[eldadfux]

@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?

[eldadfux]

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

[Ishaan28malik]

Is it still open ? @eldadfux

[CQ10]

คราบ

[eldadfux]

@CQ10 please use english.

[mbtamuli]

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

[mbtamuli]

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

[eldadfux]

@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...

[CQ10]

ดีคราบ

[eldadfux]

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

[mostafahussein]

It worth giving it a try. I will test it out and check if we need more modifications to do or it will be enough so we can integrate it with travis too

…

On Wed, Dec 4, 2019, 7:14 AM Eldad A. Fux ***@***.***> wrote: @mostafahussein <https://github.com/mostafahussein> yeah, sorry - forgot to paste the link: https://kompose.io/installation/ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#24?email_source=notifications&email_token=AA7J7PYUGWWKC5RD22OUTWTQW44D5A5CNFSM4IZOFB3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF3YF2I#issuecomment-561480425>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA7J7PZJT4A4EKQNDNF5ANDQW44D5ANCNFSM4IZOFB3A> .

[eldadfux]

@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?

[loftwah]

I'm interested to know the status of this issue.

[StarTrooper08]

Can you help me solving this issue @loftwah ??

I m learning devOps and would like to contribute to this project issue.
The things that I will by contributing to this project

• Learn Helm chart

[loftwah]

Yep definitely, are you in the Discord? I am Beatsmiff in there, if not I am easy to get in touch with and I'd love to work with you on this one.

[StarTrooper08]

Yes I m in the appwrite server.
(Atharva Shirdhankar)

[loftwah]

Wicked, PM me and we'll go from there. We can work out a time when we're both free.

[StarTrooper08]

Ok sure👍

[StarTrooper08]

But I think better discuss here openly about this issue.
If anyone else want to Help us can do it.
Personal msg will be like close discussion.

[StarTrooper08]

Even we can make GitHub discussion for the same.

[loftwah]

Oh no doubt, I was just thinking PM for scheduling, but I'm happy to do it all here, buzz me when you're online.

[loftwah]

https://github.com/kubernetes/kompose Something like this might be a good idea.

kompose is a tool to help users who are familiar with docker-compose move to Kubernetes. kompose takes a Docker Compose file and translates it into Kubernetes resources.

[loftwah]

That's okay, we could manually fill out the rest.

[Keshara1997]

i'll take this

[sumanentc]

Is AppWrite-Helm officially supported now ?
https://github.com/k3env/appwrite-helm

[Marx2]

https://k3env.github.io/appwrite-helm/index.yaml doesn't exists, so it cannot be used as repo for Helm charts

[hanbinloop]

I need the helm version of the chart

[fpoussin]

I've made an Helm chart based of https://github.com/k3env/appwrite-helm. (see #5276)
It's working for the most part but will need improvements.

Since Appwrite is so tightly bound to Docker, the function executor cannot work in the current state. (at least in a clean way)

https://github.com/fpoussin/appwrite-helm