-
Notifications
You must be signed in to change notification settings - Fork 398
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
[OSPP 2024] Build iot system configuration isolation on nodepool #1597
Labels
Comments
/assign |
/unassign |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@LavenderQAQ Do you have any progress about this issue? |
@rambohe-ch I am really busy recently. I plan to write a proposal first, which may be after March. |
Hello,I am Zhangmingyu。Please |
/assign |
WoShiZhangmingyu
added a commit
to WoShiZhangmingyu/openyurt
that referenced
this issue
Aug 19, 2024
WoShiZhangmingyu
added a commit
to WoShiZhangmingyu/openyurt
that referenced
this issue
Aug 19, 2024
WoShiZhangmingyu
added a commit
to WoShiZhangmingyu/openyurt
that referenced
this issue
Aug 22, 2024
WoShiZhangmingyu
added a commit
to WoShiZhangmingyu/openyurt
that referenced
this issue
Aug 22, 2024
WoShiZhangmingyu
added a commit
to WoShiZhangmingyu/openyurt
that referenced
this issue
Aug 22, 2024
WoShiZhangmingyu
added a commit
to WoShiZhangmingyu/openyurt
that referenced
this issue
Aug 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
Provides multiple PlatformAdmin deployment based on the same namespace, and allows users to customize the configuration of a nodepool.
Why is this needed:
We gave users the ability to customize iot systems in #1595, but it's currently not isolated enough for nodepool.
This is a very old need, refer to multi edgex instance support. OpenYurt extends the concept of nodepools on top of k8s, so an ideal deployment is that users can configure each nodepool iot system independently. With #1435 we can manipulate yurtappset to configure each nodepool individually. And service topology allows us to separate the traffic from each nodepool. With these two capabilities we can take a step closer to idealizing the current deployment model.
Finally, there is the tricky problem that we cannot split the configuration of services by nodepool (because edgex internal components access the same set of dns). At the moment we don't think there's enough incentive to solve this problem.
others
/kind feature
The text was updated successfully, but these errors were encountered: