Network

Add the possibility to get a routed ipv6 ranges. For example when you run a vpn or docker containers on your droplet it is useful to have a routed ipv6 range. By example a /64 or /56 (ripes advice)

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.

I'd like to be able to set up PTR Records for LoadBalancers similarly to Droplets.

Many people use custom images for various reasons. An additional reason now is the removal of support for FreeBSD standard images from DigitalOcean. Please enable support for IPV6 on custom images like you have IPV4 on custom images.

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.

Configurable SOA Records for DNS to change email address.

It would be really nice to be able to generate a pcap file on one of the cloud firewalls that sit in front of a droplet. This would be invaluable for troubleshooting network traffic issues.

Your firewall lacks some basic features that I expect in a firewall. Could some of these be added? Named IP address / alias - use a name for an IP address or a group of addresses instead of just the address. This would let me know at a glance who/what is allowed in a firewall. IP groups - define a group of IP addresses that can be referenced in multiple firewalls. Members of a group could be IP address, an alias/name, or another group.

It would be great to be able to put app platform instances into VPCs.

It'd like to have ability to set my PVCs as ReadWriteMany. Currently it's only ReadWriteOnce. I know, there's option to use OpenEBS for that, but having it native would be awsome. Best regards, Team of PrzypomnijMi.com