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

Kubernetes supports multiple replicas #128

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

Originally created by @pictureyong on GitHub (Jun 4, 2025).

Self Checks

To make sure we get to you in time, please check the following :)

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • "Please do not modify this template :) and fill in all the required fields."

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @pictureyong on GitHub (Jun 4, 2025). **Self Checks** To make sure we get to you in time, please check the following :) - [ ] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-plugin-daemon/issues), including closed ones. - [ ] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [ ] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [ ] "Please do not modify this template :) and fill in all the required fields." **Is your feature request related to a problem? Please describe.** A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.
yindo closed this issue 2026-02-16 00:19:59 -05:00
yindo commented 2026-02-16 00:20:00 -05:00
Author
Owner
Copy Link
Copy Source

@pictureyong commented on GitHub (Jun 4, 2025):

Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing. See document images 56/10000 for real-time translation. Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing

@pictureyong commented on GitHub (Jun 4, 2025): Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing. See document images 56/10000 for real-time translation. Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing
yindo commented 2026-02-16 00:20:00 -05:00
Author
Owner
Copy Link
Copy Source

@41tair commented on GitHub (Jun 4, 2025):

Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing. See document images 56/10000 for real-time translation. Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing

Could you please fill out your request using the template? We need more detailed information, such as what issue you encountered and in what context. I’m unable to understand what “See document images 56/10000 for real-time translation” means.

@41tair commented on GitHub (Jun 4, 2025): > Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing. See document images 56/10000 for real-time translation. Does the current service support starting multiple replicas in Kubernetes? If so, should storage sharing be implemented? Currently, there are issues with storage sharing Could you please fill out your request using the template? We need more detailed information, such as what issue you encountered and in what context. I’m unable to understand what “See document images 56/10000 for real-time translation” means.
yindo commented 2026-02-16 00:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 10, 2026):

Installing sync dependencies relies on the object-storage adapter layer (installedBucket/packageBucket), which can point to S3/MinIO/Azure Blob/GCS or any other remote store.
Multi-machine setups work perfectly as long as every node is configured to use the same bucket/prefix.
Each node’s local working directory (PluginWorkingPath) is used to unpack and build the runtime environment (.venv); it is strongly recommended that every node use its own local disk instead of a shared one. This prevents concurrency collisions; if you must share, add distributed locking.
Multi-node HA checklist
Both instances use the same remote object store:
– PLUGIN_STORAGE_TYPE set to s3/minio/azure/gcs (never “local”)
– Identical bucket, endpoint and credentials
– PLUGIN_INSTALLED_PATH and PLUGIN_PACKAGE_CACHE_PATH identical (same prefix)
PLATFORM=local; WatchDog scans the installedBucket once at start-up and then every 30 s on every node.
PluginWorkingPath must be node-local; if shared, enable distributed locking to serialize environment initialization for the same plugin.
Minimal example (two instances sharing one MinIO/S3 bucket) – environment variables must be identical on both sides.

@fatelei commented on GitHub (Jan 10, 2026): Installing sync dependencies relies on the object-storage adapter layer (installedBucket/packageBucket), which can point to S3/MinIO/Azure Blob/GCS or any other remote store. Multi-machine setups work perfectly as long as every node is configured to use the same bucket/prefix. Each node’s local working directory (PluginWorkingPath) is used to unpack and build the runtime environment (.venv); it is strongly recommended that every node use its own local disk instead of a shared one. This prevents concurrency collisions; if you must share, add distributed locking. Multi-node HA checklist Both instances use the same remote object store: – PLUGIN_STORAGE_TYPE set to s3/minio/azure/gcs (never “local”) – Identical bucket, endpoint and credentials – PLUGIN_INSTALLED_PATH and PLUGIN_PACKAGE_CACHE_PATH identical (same prefix) PLATFORM=local; WatchDog scans the installedBucket once at start-up and then every 30 s on every node. PluginWorkingPath must be node-local; if shared, enable distributed locking to serialize environment initialization for the same plugin. Minimal example (two instances sharing one MinIO/S3 bucket) – environment variables must be identical on both sides.
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#128
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?