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
Currently we have made sure the names returned by GetLoadBalancerName will satisfy the rules of GCE and AWS. In the future, we need to make this function more flexible so that different naming rules can be forced.
I think we can close this? At least on AWS, we now create the ELB with a name derived from the service UUID, so we can guarantee we meet the rules, whatever name the user chooses.
I think this is the pattern other clouds use/should use also. Closing, but feel free to reopen if not...
Cloud providers have various rules regarding the naming of a load balancer. Here are links to the rules of GCE (https://cloud.google.com/compute/docs/load-balancing/network/target-pools) and AWS(http://docs.aws.amazon.com/ElasticLoadBalancing/latest/APIReference/API_CreateLoadBalancer.html).
Currently we have made sure the names returned by GetLoadBalancerName will satisfy the rules of GCE and AWS. In the future, we need to make this function more flexible so that different naming rules can be forced.
Related: #7145 #6812
The text was updated successfully, but these errors were encountered: