-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Task] ShenYu namespace development #5623
Comments
Modifications to the Shenyu-Admin module can refer to: #5604 |
pls assign to me middleware sync |
Please assign part 1.8 to me @xcsnx |
This subtask is under discussion, and the transformation plan has not yet been determined. |
Thank you for your response. I understand that subtask 1.8 is still under discussion. If there's anything I can help with, please let me know. Thank you! |
Hello, the modification plan for Apidoc has been finalized. The plan is to decouple Apidoc from selector and rule. Can you handle this subtask? |
Hello, Thank you for the update. I am very interested in this task and would like to take it on. Looking forward to contributing! Best regards, Siheng Yu |
pls assign part 1.8 to me |
Description
Currently, managing multiple user requirements with ShenYu often involves deploying multiple ShenYu Admin instances and sets of ShenYu Gateway. To ensure data independence, each gateway typically connects to only one ShenYu Admin. However, managing multiple ShenYu Admin instances increases both user and operational costs.
With ShenYu Admin's namespace feature, users can deploy a single ShenYu Admin cluster to manage multiple ShenYu Gateways. The namespace management allows for better control of ShenYu Gateway and ShenYu Client data registration, reducing both user and operational costs.
Task List
1.Shenyu-Admin:
2.Shenyu-client:
3.Sync data :
The text was updated successfully, but these errors were encountered: