kovagoadi/hunfabric
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add peering config via GKE module to hub and spoke peering README

Browse Source
This commit is contained in:
Ludovico Magnocavallo
2020-04-25 07:34:01 +02:00
parent d0c1da87a1
commit 6a75a3d2be
1 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
infrastructure/hub-and-spoke-peering/README.md
View File

@@ -41,7 +41,24 @@ gcloud container clusters get-credentials cluster-1 --zone europe-west1-b
kubectl get all
```
The next step is to edit the peering towards the GKE master tenant VPC, and enable export routes. The peering has a name like `gke-xxxxxxxxxxxxxxxxxxxx-xxxx-xxxx-peer`, you can edit it in the Cloud Console from the *VPC network peering* page or using `gcloud`:
The next step is to edit the peering towards the GKE master tenant VPC, and enable export routes. You can do it directly in Terraform with the GKE module `peering_config' variable, via gcloud, or on the cloud ccnsole. We're leaving it as an option, since one of the goals of this example is to allow testing both working and non-working configurations.
### Export routes via Terraform
Change the GKE cluster module and add a new variable after `private_cluster_config`:
```hcl
peering_config = {
export_routes = bool
import_routes = bool
}
```
If you added the variable after applying, simply apply Terraform again.
### Export routes via gcloud
The peering has a name like `gke-xxxxxxxxxxxxxxxxxxxx-xxxx-xxxx-peer`, you can edit it in the Cloud Console from the *VPC network peering* page or using `gcloud`:
```
gcloud compute networks peerings list