[Bug] Dify - worker pod is running with MODE=api

[bayerhazard]

Please Provide the basic information of the app

Dify

App URL in Olares Market(Required)
https://market.olares.com/app/market.olares/difyv2

Describe the bug

The worker pod is running with MODE=api, acting as a second API server instead of a Celery worker. The document queue is waiting for a consumer that never arrives.

To Reproduce

• OS Version: 1.12.5
• Browser Safari
• Steps to reproduce the behavior:
  • Initial install of Dify from Market
  • create a new knowledge base
  • add document and start processing -> document will not process but stays in status queued

Expected behavior
A document added to the knowledge based should be embedded.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
With the next release, please change MODE=api to MODE=worker in the ConfigMap.

[bayerhazard]

Second Issue:
The weaviate Service in difyv2server-shared only exposes port 8080 (HTTP). Port 50051 (gRPC) is missing. Dify's worker communicates with Weaviate via gRPC for batch object ingestion, causing all embedding tasks to fail with StatusCode.UNAVAILABLE and retry indefinitely. Documents are stuck at 0% during the embedding phase.

Fix applied manually
kubectl patch service weaviate -n difyv2server-shared --type merge -p '{"spec":{"ports":[{"name":"http","port":8080,"protocol":"TCP","targetPort":8080},{"name":"grpc","port":50051,"protocol":"TCP","targetPort":50051}]}}'

[bayerhazard]

Third and Fourth Issue:
Error: too many DB connections: SQLALCHEMY_POOL_SIZE reduced to 5
Login broken after first Patch: MODE=api as override directly in API-Deployment