From c48f6130e6a8b2d675f8f0c6750fce20275243b3 Mon Sep 17 00:00:00 2001 From: Ludovico Magnocavallo Date: Sat, 25 Apr 2020 07:47:12 +0200 Subject: [PATCH] Update README.md --- infrastructure/hub-and-spoke-peering/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/infrastructure/hub-and-spoke-peering/README.md b/infrastructure/hub-and-spoke-peering/README.md index d89814477..1ad0aba98 100644 --- a/infrastructure/hub-and-spoke-peering/README.md +++ b/infrastructure/hub-and-spoke-peering/README.md @@ -71,7 +71,9 @@ Then connect via SSH to the spoke 1 instance and run the same commands you ran o ## Operational considerations -A single pre-existing project is used in this example to keep variables and complexity to a minimum, in a real world scenarios each spoke would probably use a separate project. +A single pre-existing project is used in this example to keep variables and complexity to a minimum, in a real world scenario each spoke would use a separate project (and Shared VPC). + +A few APIs need to be enabled in the project, if `apply` fails due to a service not being enabled just click on the link in the errr message to enable it for the project then resume `apply`. The VPN used to connect the GKE masters VPC does not account for HA, upgrading to use HA VPN is reasonably simple by using the relevant [module](../../modules/net-vpn-ha).