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

Support Hetzner Cloud Load Balancers #93

Open
ceelian opened this issue Jun 23, 2020 · 7 comments
Open

Support Hetzner Cloud Load Balancers #93

ceelian opened this issue Jun 23, 2020 · 7 comments

Comments

@ceelian
Copy link

ceelian commented Jun 23, 2020

Just saw that Hetzner has now Cloud Load Balancers (beta). Would be a nice addition for the rancher driver as well at some point.

Info: https://www.hetzner.com/news/07-2020-load-balancer/

Product Page: https://www.hetzner.com/cloud/load-balancer

Cloud Controller: https://github.com/hetznercloud/hcloud-cloud-controller-manager

@ceelian ceelian changed the title Info: Hetzner now has Cloud Load Balancers Add Hetzner Cloud Load Balancers Jun 23, 2020
@ceelian ceelian changed the title Add Hetzner Cloud Load Balancers Support Hetzner Cloud Load Balancers Jun 23, 2020
@eramahatra
Copy link

use case :
when a server is deleted, it's detached from the LB
Once created again with rancher, it should be automatically assigned to a given LB.
Note : LB should be assigned on the Worker nodes and not the Master nodes

@ceelian
Copy link
Author

ceelian commented Jun 29, 2020

@eramahatra personally I would suggest it even more simple. A LB is created when a new cluster is created, Loadbalancer is infront of all nodes because you could have mixtures of worker/master nodes or even change that after creation. When Cluster is deleted, LB is deleted as well.

@anebi
Copy link

anebi commented Jul 1, 2020

I don't think that autocreation of LB should be done, because this is a paid service and someone would like to use built in nginx instead of LB or to use cheaper frontend servers with haproxy or nginx instead of LB. Using Hetzner LB must be optional.

Other than that, I agree that if LB usage is requested then nodes assignment/removal must be automated. Also it would be great if there is a way to disable LB in edit cluster option and go back to simple rancher nginx usage if user wants to get rid of LB.

Another thing that should be checked and considered is CloudFlare and another DNS features that Rancher has. When LB is used, then the DNS records that are created on DNS providers must use the LB IP address/domain name instead of worker nodes ip addresses.

@haswalt
Copy link

haswalt commented Aug 17, 2020

We've created a small pod that runs as a daemonset on all nodes. It simply adds nodes to the LB when they start and removes them when stopped.

If there's any interest in this as a solution I'll publish it on GitHub.

@spatialy
Copy link

We've created a small pod that runs as a daemonset on all nodes. It simply adds nodes to the LB when they start and removes them when stopped.

If there's any interest in this as a solution I'll publish it on GitHub.

Hi @haswalt can you publish your solution? We are using MetalLB but think for some uses cases this is over-complex.

Best

@haswalt
Copy link

haswalt commented Sep 20, 2020

@spatialy yes i'll prepare something for early next week.

@haswalt
Copy link

haswalt commented Sep 20, 2020

@spatialy actually did it already: https://github.com/BlueBambooStudios/hcloud-connect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants