langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

How to deploy with high availability or scale up? #32

New Issue
Closed
opened 2026-02-16 00:19:15 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 00:19:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @huhamhire on GitHub (Mar 10, 2025).

Is there any examples for deploying dify plugin daemon with high availability?

I need to run the plugin daemon in a relatively large project in kubernetes cluster without serverless runtime.

Since the plugin daemon in local mode is not a stateless service, how to scale up while managing local plugin storage correctly？

In pre 1.0 versions, with everything packed in the released container, I could just scale up worker / api services.

Originally created by @huhamhire on GitHub (Mar 10, 2025). Is there any examples for deploying dify plugin daemon with **high availability**? I need to run the plugin daemon in a relatively large project in kubernetes cluster without serverless runtime. Since the plugin daemon in local mode is not a stateless service, how to scale up while managing local plugin storage correctly？ In pre 1.0 versions, with everything packed in the released container, I could just scale up worker / api services.
yindo closed this issue 2026-02-16 00:19:15 -05:00
yindo commented 2026-02-16 00:19:16 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (Mar 10, 2025):

For high availability, you do need to use a serverless platform instead of using daemon, which is a standalone, as daemon itself has no permission to access cgroups/seccomp/containerd, it's not designed for high availability.

@Yeuoly commented on GitHub (Mar 10, 2025): For high availability, you do need to use a serverless platform instead of using daemon, which is a standalone, as daemon itself has no permission to access cgroups/seccomp/containerd, it's not designed for high availability.
yindo commented 2026-02-16 00:19:16 -05:00
Author
Owner
Copy Link
Copy Source

@brightwang commented on GitHub (May 4, 2025):

For the high availability deployment of the plugin daemon, you can refer to this video of mine.
https://www.bilibili.com/video/BV1AbdeY7Ebs/?spm_id_from=333.337.search-card.all.click

@brightwang commented on GitHub (May 4, 2025): For the high availability deployment of the plugin daemon, you can refer to this video of mine. https://www.bilibili.com/video/BV1AbdeY7Ebs/?spm_id_from=333.337.search-card.all.click
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#32
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?