-
Notifications
You must be signed in to change notification settings - Fork 407
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
[vote] the name of component that provide governance ability in nodepool. #786
Comments
sheepdog+1 |
sheepdog +1 |
1 similar comment
sheepdog +1 |
yurt-minister: yurt大臣/使节 |
pool-coordinator+1 |
sheepdog +1 |
pool-coordinator +1 |
sheepdog +1 |
shepherd +1 |
sheepdog +1
I totally agree the opinion, and that is one of the reasons I prefer "sheepdog". Because this new component is used for nodepool-level autonomy when there're some nodes(sheep) offline. It will not replace the API Server(shepherd) at the cloud, which has stronger capability and manages the whole cluster, and only serve as an assistance. |
yurt-minister +1 |
Thanks for your reply. Maybe I have some misunderstanding about the project name or the role of this new component. |
@ujnzxw Very appreciate for your reply. we will keep this vote until 4.1(Friday) and wait for more discussion and vote. |
yurt-minister +1 |
pool-coordinator +1 |
1 similar comment
pool-coordinator +1 |
shepherd +1 |
pool-coordinator + 1 |
new proposal: |
pool-coordinator + 1 |
pool-coordinator +1 or new proposal: pool-harbor |
sheepdog+1 |
yurt-minister+1 |
pool-coordinator + 1 |
more than 20 people have already voted, and the top three names are:
so according to the voting rules, |
What would you like to be added:
In the proposal, a new component(named pool-spirit) will be added in the edge NodePool. the new component mainly provides the following ability:
For these abilities, the name
pool-spirit
maybe make end user confused, so OpenYurt community have decided to rename the new component. all candidate names as following:please select your favourite name and reply this issue.
btw: other names for new component are also welcome.
The text was updated successfully, but these errors were encountered: