Add documentation for load balancer changes (#2336)
--------- Co-authored-by: Ludovico Magnocavallo <ludomagno@google.com>
This commit is contained in:
committed by
GitHub
parent
3487cb8c71
commit
ea564df648
@@ -11,6 +11,7 @@ This module allows managing a GCE Internal Load Balancer and integrates the forw
|
||||
- [Dual stack (IPv4 and IPv6)](#dual-stack-ipv4-and-ipv6)
|
||||
- [PSC service attachments](#psc-service-attachments)
|
||||
- [End to end example](#end-to-end-example)
|
||||
- [Deploying changes to load balancer configurations](#deploying-changes-to-load-balancer-configurations)
|
||||
- [Issues](#issues)
|
||||
- [Variables](#variables)
|
||||
- [Outputs](#outputs)
|
||||
@@ -347,6 +348,10 @@ module "ilb" {
|
||||
# tftest modules=3 resources=7 e2e
|
||||
```
|
||||
|
||||
## Deploying changes to load balancer configurations
|
||||
For deploying changes to load balancer configuration please refer to [net-lb-app-ext README.md](../net-lb-app-ext/README.md#deploying-changes-to-load-balancer-configurations)
|
||||
|
||||
|
||||
## Issues
|
||||
|
||||
There are some corner cases where Terraform raises a cycle error on apply, for example when using the entire ILB module as a value in `for_each` counts used to create static routes in the VPC module. These are easily fixed by using forwarding rule ids instead of modules as values in the `for_each` loop.
|
||||
|
||||
Reference in New Issue
Block a user