Skip to content
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] name the edge load balancer agent: seeking suggestion for name #2023

Open
wangxye opened this issue Apr 16, 2024 · 4 comments
Open

[vote] name the edge load balancer agent: seeking suggestion for name #2023

wangxye opened this issue Apr 16, 2024 · 4 comments
Labels

Comments

@wangxye
Copy link
Member

wangxye commented Apr 16, 2024

What would you like to be added:
The Edge Load Balancing Agent is designed to support load balancing of edge nodes in the node pooling dimension, which is deployed in each node to route request traffic forwarding for services in the node pooling dimension with virtual IPs via Keepalived.

Specifically, in the deployment of load balancing services for edge nodes, it lists/watches the creation, update, and deletion of the poolservice, and for the virtual router ID (VRID) assigned by the load balancing controller to modify the configuration of the Keepalived on the specified node within the node pool.

We invite suggestions for a new name for the edge load balancer agent.
Please feel free to provide a suitable name in response to this issue.

@wangxye wangxye added the kind/feature kind/feature label Apr 16, 2024
@gnunu
Copy link
Member

gnunu commented Apr 17, 2024

If the LB feature is named LBSet, the class name can be named after their implementation. In this case, Keepalived.

@vie-serendipity
Copy link
Contributor

vie-serendipity commented Apr 17, 2024

YurtAlived, alive represents keepalived, d represents daemonset. Anyway, I think the name should be related to keepalived since it's an implementation of a specific load balance class, whereas LBAgent sounds like it's connected to a higher-level controller.

@rambohe-ch
Copy link
Member

how about name this new component as YurtVIPBroker?

The name implies that the component acts as a broker for VIPs within the OpenYurt, ensuring that their allocation, release, and synchronization are handled properly, facilitating high availability and consistent service networking.

Copy link

stale bot commented Jul 18, 2024

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.

@stale stale bot added the wontfix label Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4 participants