caicloud / loadbalancer-controller

Kubernetes loadbalancer controller to provision ingress controller dynamically

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Node selection

zjx-caicloud opened this issue · comments

Refactor(taint):

What happened:
Loadbalancer-controller lets users or loadbalancer-admin to decide which nodes to place proxies, it is not practical because only cluster admins know which nodes are suitable.

What you expected to happen:
Cluster admins taint suitable nodes previously, users or loadbalancer-admin need only to set number of proxies they need, no more which nodes they need.

Could you please give me a concrete design to implement this? @zoumo .

And I think the refactor may affect codes of:

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close