Scalable compute services.
Simple object storage.
Run managed Kubernetes clusters.
Tools & Integrations
Automate your infrastructure.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Private networking is currently limited to droplets running in the same datacenter. It would be great if it would be possible for the droplets to connect to the internal IP's in other datacenters too!
I'm in a similar situation as another user - I have a Consul, Vault and Nomad clusters setup. I can't accomplish the best HA setup without this feature.
At the very least it should work NYC 1 to NYC 3.
This is a fundamental feature for reliable and redundant cloud applications. To have a HA cluster with docker swarm, kubernetes, mongodb and many other software, you need at least three nodes in three AZ: without this feature real HA can't be reached for these tools.
This is highly needed for true redundant setups across regions. Would be awesome to see this implemented. Traffic could count towards the total outgoing bandwidth
It would be no problem for me to count the traffic between datacenters against the droplets traffic limit or pay extra for it.
Yes! Please, please. I want to have a backup server in a different region and/or datacenter but be able to synchronize files, database,etc privately.
You won't be notified about changes to this idea.