192
allow Floating IPs to point to load balancers
under review
J
Jonathan Paugh
This would allow me to scale an app seamlessly in real time, instead of needing to carefully time it against DNS cache latency.
After playing around with the new Load Balancers for a bit, It seems like an obvious extension. By the way, I'm really pleased with the feature. It seems very polished.
Activity
Newest
Oldest
M
Marco Wuethrich Pr
Same problem here. I run a digitalOcean Kubernetes cluster (DOK) with a digitalOcean LoadBalancer as a public gateway to the outside world. Our customers point to the public IP of the LoadBalancer with a DNS record.
I find the statement that you should just not delete the load balance quite amusing.
I have already managed once that I accidentally screwed something to the config in the cluster and thereby the loadBalancer no longer worked, only a delete/create... helped. And the consequences were some DNS records changes. Luckily we didn't have many customers on it yet.
This feature prevents us from scaling up the cluster and putting more customers on it. Too big is the fear that the public IP will change.
Michał
It's mind boggling this is still not a thing - DigitalOcean's own documentation [1] recommends using a Floating IP before 2 load balancers for high availability, yet it is not possible to point a Floating IP and the DO managed LoadBalancer.
Please consider fixing this DO, thanks!
Shashank
This is super critical for my application because our customers use naked custom domains to point to our fixed IP address. Currently, I use a single droplet and plan to increase the fleet size by adding more droplets and a load balancer.
I have to retain the same IP address so as to not break the custom domains flow and having the ability to assign the floating IP to a load balancer allows me to scale horizontally.
V
Vito Meznaric
100% agree with Shashank. The fact that we cannot assign static IPs to load balancer eliminates entire class of apps - want customers to link their domains to our service? Can't do, because IP might change and it will break customers' websites.
DO gave me everything I need, but the last piece of really solid infrastructure.
Shashank
Vito Meznaric: Yeah, this is the most important feature for me otherwise, I will have to move somewhere else.
Merged in a post:
Allow assigning a floating ip to a load balancer
G
Giannis Sialmas
Due to some tests i am doing, I am scraping and recreating a k8s cluster multiple times per day, and each time i create a new load balancer. The floating ip is the only option of "static ip" i can get on digital ocean and want to be able to point it to a new load balancer programatically. Sure i can point a dns at the load balancer, but i dont like the propagation
This post was marked as
under review
ByteLoch Services
We totally need this? I'm not sure why it is not an already implemented feature? Or am 'I missing something? What is the alternative to managing this situation? Any help documentation on this please?
Our company is using Istio for LB related stuff (IaC via Terraform), so when our cluster is updated as it means we lose the external-ip that is assigned to it. Would be very helpful to have this feature.