this is related to #134
This PR is making the load_balancer module more flexible by:
allowing to have multiple global lbs
making tcp router optional (default is true)
using count straight forward
Variables url_map_name, http_proxy_name, https_proxy_name, http_forwarding_rule_name and https_forwarding_rule_name were introduced to keep it backwards compatible.
Therefore all existing objects and names are kept, hence no update to existing deployments is required!
if merged, I would make consecutive PRs for adding an optional LB for service mesh (service mesh branch) and refactor isolation segment module to also use the load_balancer module (isoseg branch).
this is related to #134 This PR is making the load_balancer module more flexible by:
Variables
url_map_name,http_proxy_name,https_proxy_name,http_forwarding_rule_nameandhttps_forwarding_rule_namewere introduced to keep it backwards compatible.Therefore all existing objects and names are kept, hence no update to existing deployments is required!
if merged, I would make consecutive PRs for adding an optional LB for service mesh (service mesh branch) and refactor isolation segment module to also use the load_balancer module (isoseg branch).