sparse-intern-71089
10/17/2018, 11:32 AMcreamy-potato-29402
10/17/2018, 3:30 PMwhite-balloon-205
external: false
(which is the default) then I believe only an internal load balancer will be allocated - so the service will not be exposed publicly.
We plan to move over to DNS service discovery for these not-exposed services. See https://github.com/pulumi/pulumi-cloud/issues/441.tall-monitor-77779
10/17/2018, 3:41 PMcloud-aws:usePrivateNetwork: "true"
makes a difference but seems to still create a load balancer, in the instance of fargate, it is possible to set load balancer to nonetall-monitor-77779
10/17/2018, 6:43 PMexternal
is not set but you can access the service via the exported hostname
tall-monitor-77779
10/17/2018, 6:44 PMexternal
on the ContainerPort
?tall-monitor-77779
10/17/2018, 6:46 PMcloud-aws:usePrivateNetwork: "true"
seems to have a better result but I think its a good idea to be able to disable the load balancer and also probably some kind of control of the Service Discovery/DNSwhite-balloon-205
tall-monitor-77779
10/17/2018, 8:51 PMtall-monitor-77779
10/22/2018, 6:54 PMtall-monitor-77779
10/22/2018, 6:56 PMshared
lib for getOrCreateNetwork
and getCluster
and the references to external config makes it very difficult to inject into if you want to do something ‘slightly’ custom