Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hi,
The “Send Outbound Traffic Over a Reserved IP” (https://docs.digitalocean.com/products/networking/reserved-ips/how-to/outbound-traffic/) document mentions for custom images that there is no anchor IP, but yet that is what must be used to send traffic out over the reserved IP.
The explanation of Anchor IP (from https://docs.digitalocean.com/glossary/anchor-ip/), says “Droplets created from custom images do not require an anchor IP to use a reserved IP, instead the reserved IP maps to the Droplet’s public IP address by default.”
I’m trying to confirm if it is tested and expected to work that custom images can send outbound traffic over a reserved IP? And if so, do they need to go through the instructions to enable Anchor IPs (https://docs.digitalocean.com/products/networking/reserved-ips/how-to/enable-old/#enable-anchor-ips-immediately)?
I was able to find an Anchor IP, but was having trouble getting routing to work (but I’m new to custom images and having multiple network ports - I see the the loopback, public IP and private IP before I try to add anchor IP).
I likely have something wrong in my setup, but just wanted to confirm it should be possible.
Thanks!
Arnold Hendriks
Scott Hilbert
jessicakaren907
Arnold Hendriks
Jules Raffoux
Drillgon200
patrickhasting
afdaldev
business