Sam Brown
On this doc: https://docs.digitalocean.com/products/networking/reserved-ips/how-to/find-anchor-ips/
Make it clearer that the IP in the curl commands is actually a genuine DigitalOcean owned IP and that the user needs to hit the curl command as in the example, whilst SSH'd into the droplet.
I was getting confused thinking that my droplet had a metadata API exposed so was changing the IP for my droplet's own IP and curling it externally.
Also, have an example of the full set anchor metadata; if the user uses an IP other-than the
anchor gateway
IP in the next command, they'll get disconnected and have to power cycle the droplet. This could be avoided with some improved docs.
Thanks!