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.

So far, load balancers only get an IPv4 and no IPv6. In practice, this means that load balancers cannot be used if you want to provide IPv6 connectivity. I would love to use this feature, but only if IPv6 was made available.

It would be great to have the possibility to set "SameSite=None" for Load Balancers with Sticky sessions enabled. It's necessary when using iframes in a cross domain situation.

I'm loving that you have Floating IPs now and I'd like to setup reverse lookups (PTR) for them.

We'd like to use floating IPs to seamlessly move traffic from one droplet to another when re-deploying services. However, we also aim to support IPv6 and already receive a lot of traffic via v6. As floating IPs are IPv4 only, this severely limits their ability to achieve their purpose in our scenario, forcing us to rely on slowly propagating DNS updates for a growing portion of our incoming traffic. Pleas add floating IPv6 Addresses.

When destroying a droplet there's a 99% chance that you will get your IP back. If someone creates a droplet while destroying/creating a new one and steals your IP, it's a pain, even if the chances are <1%. This 1% is too much for some. An IP is an important number, your server might not be able to send emails if the last IP's user was sending spam through it. Software licenses are also tied to IP sometimes. When I want to rebuild a server (or resize: disk size) I want to make sure that I get my IP back. Please figure out a way so that we don't lose our IP (100% guaranteed) when we destroy/recreate a droplet.

floating/reserved ips it should be possible to tag them like you would droplets. as a minimum this would help with metadata about the reserved ips. for example any ip tagged 'prod' can only be used for prod services

Other posts have commented on the cost of providing extra IPv4 IPs. It strikes me many users may not actually need a public IP for their usage, and if appropriately incentivised would choose not to use one.

Remove requirement for public IP. Not all droplets need to have a dedicated public IP address. Instead, allow us to have 1 gateway per VPC that the droplets can reach the Internet from.

Hello Would be nice to have support for IPSec-ESP (50) and IPSec-AH (51) protocols in DigitalOcean Firewall. Currently I have to use iptables since DO FW is limited to TCP, UDP and ICMP