-
Notifications
You must be signed in to change notification settings - Fork 404
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
UnitedDeployment usages #124
Comments
@hle2 good idea, In the edge scenario, the distribution of worker nodes is relatively scattered. There may only be one worker node at the same physical location, and there may also be multiple worker nodes at the same physical location. However, multiple worker nodes are differentiated in OS, CPU architecture or network. Therefore, from the work Node resource perspective of edge nodes, they need to be divided into different Nodepool to represent the same set of features. All under the same nodepool node should have the same label, the annotation and taint, so k8s native resources (deployment, statefulset daemonset) easy deployment. In order to enable k8s native Deployment, Statefulset,daemonset resources to deploy intelligently according to NodePool, we abstract the concept of UnitedDeployment which is a k8s crd. In the definition of UnitedDeployment, we support deployment, Daemonset, statefulSet resources can deploy to different Nodepool in one model. @charleszheng44 and I are working on it and will submit a proposal later. |
@kadisi, Thanks much for the comments! |
yes, NodePool is also defined as a CRD, we will later add a |
@hle2 UnitedDeployment has been released, and the repo is here: https://github.com/openyurtio/yurt-app-manager |
@rambohe-ch thanks much for the information! |
Would like to understand how UnitedDeployment can be used?
The text was updated successfully, but these errors were encountered: