Open malston opened 6 years ago
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
Hi @malston, thanks for the PR!
According to the Reference Architecture you're supposed to configure only a load balancer for your Go Router in your Isolation Segment. The Diego SSH and TCP Router Load balancers come from the Shared Isolation Segment, therefore you don't need to create additional Diego SSH nor TCP Router LBs.
Could you please remove them from the PR, as well as address the aforementioned reviews, then we'll get it merged. Thanks again for the PR!
cc @ciriarte
@cdutra @malston I fixed a few issues that kept this from applying and added in the network security groups for isolation segments.
iso_seg_names
and iso_seg_subnets
having len > 0.I validated that I successfully deploy an isolation segment using the new isolation segment templates in this PR. I deployed an iso segment and was able to push an app to it.
For each segment it will: