How to deploy based on kubernetes？

[tuninger]

Describe your problem

How to deploy based on kubernetes? What I mean is that ragflow is currently supported to be deployed through docker-compose. When will it be supported to deploy ragflow through helm charts or yaml files?

[Kraego]

kustomize would be nice too

[janineguo]

@KevinHuSh Are there any updates on this feature? I have converted all the Docker Compose files to YAML format. If this feature is still being addressed, I can take care of this task and use Helm to make it easier to install on Kubernetes.

[steffenboe]

@janineguo maybe submit a PR for this? would love to have this as well!

[KevinHuSh]

Not any updates yet.

[nakroy]

Not any updates yet.

I'm working on creating a helm chart for RAGFlow. I have some questions about the version of dependencies, like MySQL, redis, MinIO and so on. Whether there's a specific version of these dependencies? Or just using the latest version is OK?

[KevinHuSh]

I think latest version is OK.

[danialkhatib]

Not any updates yet.

I'm working on creating a helm chart for RAGFlow. I have some questions about the version of dependencies, like MySQL, redis, MinIO and so on. Whether there's a specific version of these dependencies? Or just using the latest version is OK?

would be nice 👌

[ayushin]

It would help to have a docker-compose / containers that run a single process /service per container i.e. server, task manager etc instead of all of them together. Once that is done a helm chart can be generated by claude.ai in minutes.

I think having services segregated in the main repo docker-compose would really help to maintain integrity.

[yuzhichang]

@nakroy docker-compose.yml records the version of dependencies(MySQL, redis, MinIO, ElasticSearch)

[nakroy]

@nakroy docker-compose.yml records the version of dependencies(MySQL, redis, MinIO, ElasticSearch)

I get it. Last two weeks I use deployments yaml files to deploy RAGFlow and it works. One little problem would be the service_conf.yaml, it needs to be dynamic created in kubernetes environment because the host of these services are used with kubernetes service domains

[s-khaon]

I'll provide you with an idea. Use the 'docker compose config' command to export the configuration to a file, and then use the 'kompose convert -f file -o path' command to get the desired deployment, daemonset, service, and pvc. If needed, I can provide a PR after adjusting the Values ​​file.