New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any project or plan to pack the Fusio into Helm Charts? #511
Comments
Hi @wdhwang currently we have no Helm chart but in general this is a good idea, we should add this to our docker repo s. https://github.com/apioo/fusio-docker |
Thank you for your response, hope to see it soon. |
Hi, I am trying run Fusio on K8s, so I modified 'docker-compose.yml' in the following steps.
After docker-compose.yml modified, and use 'kompose' to create K8s resource files. And execute the following commands. kubectl apply -n fusio -f k8s/fusio-service.yaml kubectl apply -n fusio -f k8s/worker-java-deployment.yaml #kubectl apply -n fusio -f k8s/fusio-default-networkpolicy.yaml_ Finally, I could let Fusio running on K8s. I am not sure this is useful for the project or not. Just sharing with you. |
Hi, I am trying to create helm chart from K8s resource files after Fusio could run on K8s. But I found there were no files of Fusio under the directory of /var/lib/mysql/fusio in the Pod of MySQL. |
I found the reason why the helm charts did not work. Because the service name in 'metadata' section was too long in the generated YAML file by helmify. So I removed all '{{ include "fusio-helm.fullname" . }}' from all YAML files. After testing, I think the attachment zip file worked. If you are free, you may test it. |
Thanks for the feedback and testing, I will try it out and see whether everything works, in general would it be ok for you if I add this to our https://github.com/apioo/fusio-docker repository? |
Of course, you can. I hope this is helpful. |
Any update? |
Hi. I am trying to manage all containers by Helm Charts.
Is there any project or plan to pack the Fusio into Helm Charts?
Thanks & regards
The text was updated successfully, but these errors were encountered: