Dalton Hubble 7c6ab21b94 Isolate each DigitalOcean cluster in its own VPC ... * DigitalOcean introduced Virtual Private Cloud (VPC) support to match other clouds and enhance the prior "private networking" feature. Before, droplet's belonging to different clusters (but residing in the same region) could reach one another (although Typhoon firewall rules prohibit this). Now, droplets in a VPC reside in their own network * https://www.digitalocean.com/docs/networking/vpc/ * Create droplet instances in a VPC per cluster. This matches the design of Typhoon AWS, Azure, and GCP. * Require `terraform-provider-digitalocean` v1.16.0+ (action required) * Output `vpc_id` for use with an attached DigitalOcean loadbalancer		2020-06-28 23:25:30 -07:00
..
aws.md	Use a route table with separate (rather than inline) routes	2020-02-25 23:21:58 -08:00
azure.md	Add new load balancing, TCP/UDP, and firewall docs/diagrams	2019-08-03 11:50:03 -07:00
bare-metal.md	Add new load balancing, TCP/UDP, and firewall docs/diagrams	2019-08-03 11:50:03 -07:00
concepts.md	Add/update docs for asset_dir and kubeconfig usage	2019-12-05 22:56:42 -08:00
digitalocean.md	Isolate each DigitalOcean cluster in its own VPC	2020-06-28 23:25:30 -07:00
google-cloud.md	Add new load balancing, TCP/UDP, and firewall docs/diagrams	2019-08-03 11:50:03 -07:00
operating-systems.md	Upgrade docs packages and refresh content	2020-05-20 23:31:26 -07:00