-
Access Logs to Spaces
Please add a feature where we can enable saving load balancer logs to a bucket on DO Spaces. This would really help clients with doing analysis and monitoring.0
-
SSL Redirect with 301 , not 307
Hello @DigitalOcean. I have idea to make redirect http to https will be with 301 , not 307. Here you can see all arguments why 301 is better with 307. https://blog.hubspot.com/blog/tabid/6307/bid/7430/what-is-a-301-redirect-and-why-should-you-c...0
-
Support TLS 1.3 on load balancers
Now the final specification of TLS 1.3 has been published and all major browsers support it, DO load balancers should support this protocol too. Work around would be to do the SSL offloading on your application servers, and with the recent proxy ...0
-
Possibility to add tags to Load Balancer - the same way as for Droplets
When you create a lot of Droplets, LoadBalancers, etc. you possibly would like to have them grouped together - so that's where tags came. Also Load Balancers spawned from Kubernetes Clusters (because of the usage of K8S service with type LoadB...0 Planned
-
Alert for Load Balancer's Health Parameter
I want to receive email alerts if the number of healthy droplets fall below my chosen threshold.0
-
Add Internal IP Address
We have setup a couple of droplets with some general API code, we use for our sites. Some of our sites are outside of Digital Ocean and some sites are within Digital Ocean. It would be great connect our Digital Ocean servers to the load balancer...0
-
Hot spare setup
Hot spare setup uses an active/passive configuration, redirecting traffic to a droplet based on its status. This creates a redundancy where traffic is redirected to a secondary droplet if the primary goes down.0
-
TLS for non-HTTPS
Would be great to be able to create forwarding rules for TCP with TLS – pointing to a cert. Providing DO uses HAproxy internally, it shouldn't be too difficult. -
Protect load balancer with cloud firewall
it would be great if load balancers will be protected too as droplets.1
-
Support HTTP/1.1 Healthchecks in Loadbalancer
Some modern microservice proxy/loadbalancer solutions do not support http/1.0 at all anymore (envoy, istio). when a http/1.0 query is submitted, they just answer with HTTP 426 UPGRADE REQUIRED in trying to force the client to use at least http/1.1...0