search

BorisPolonsky / dify-helm

Deploy langgenious/dify, an LLM based app on kubernetes with helm chart
MIT License
132 stars 30 forks source link

EKS failed because EBS does not support `ReadWriteMany` mode #8

Closed Imccccc closed 12 months ago

Imccccc commented 12 months ago

I am not sure it is a good idea that api and worker share the same path.

BorisPolonsky commented 12 months ago

I am not sure it is a good idea that api and worker share the same path.

It's implemented this way according to the api and worker section in official docker-compose.yaml. We haven't gone through code detail in dify so you may wish to submit issues in official repo to opt out possible path collision in the application in case path are shared.

As for the problem stated in the title (EKS failed because EBS does not support ReadWriteMany mode), could you elaborate and clarify the steps to replicate your issue. From our understanding there are multiple components that need PVC deployed. If it's related to redis, postgresql, these dependencies inherit charts published by bitnami. You may opt in external redis and postgresql to solve that. As for the storage for api and worker, you may use external S3 instead of PVC, or switch to any PVC that supports ReadWriteMany. If you could confirm modes other than ReadWriterMany that are practical in this case, please let us know.

Imccccc commented 12 months ago

Cause EKS default storage class gp2 using EBS as backend, and EBD only mounted on one node. I changed the storage class backed by EFS, the problem solved. EFS driver reference is here: efs-csi

BTW thanks for the help.