You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found in modules/net-lb-int when applying end-to-end example, but this may affect also other Load Balancer modules:
Error creating RegionBackendService: googleapi: Error 400: Invalid value for field 'resource.backends[0].balancingMode': 'UTILIZATION'. Balancing mode must be CONNECTION for an INTERNAL backend service., invalid
Cross checked with docs and analysis for each of the module below.
net-lb-int
This are allowed values (according to docs) for Internal passthrough Network Load Balancer
## net-lb-int
* Fix error on apply of example:
```
Error creating RegionBackendService: googleapi: Error 400: Invalid value for field 'resource.backends[0].balancingMode': 'UTILIZATION'. Balancing mode must be CONNECTION for an INTERNAL backend service., invalid
```
* remove unused `balancing_mode` variable, as only one value is possible anyhow
## net-lb-ext
* update in the `backends` description
## net-lb-proxy-int
* update in the `backends` description
## net-lb-app-int
* added validation of `balancing_mode`
* fixed other validations
## net-lb-app-ext
* added validation of `balancing_mode`
* fixed other validations
* removed validation for `locality_lb_policy` as this variable is not used in this module
Closes: #1767
Found in
modules/net-lb-int
when applying end-to-end example, but this may affect also other Load Balancer modules:Cross checked with docs and analysis for each of the module below.
net-lb-int
This are allowed values (according to docs) for Internal passthrough Network Load Balancer
change defaults where current default value is not usable?net-lb-ext
Only
CONNECTION
allowed per docs, but no changes necessary as this attribute is not controlled by module inputs.UTILIZATION
net-lb-proxy-int
OK
net-lb-app-int
OK. Can add vallidation:
net-lb-app-ext
OK. Can add vallidation:
The text was updated successfully, but these errors were encountered: