search

Capgemini / Apollo

:rocket: An open-source platform for cloud native applications based on Apache Mesos and Docker.
http://capgemini.github.io/devops/apollo/
MIT License
723 stars 105 forks source link

Solution for internal services #436

Open enxebre opened 9 years ago

enxebre commented 9 years ago

So the way it is at the moment as the haproxy template is very simplistic every service will be exposed to the outside as service-name.example.com via the elb using the port 80 both the elb and the haproxies. Could create another "haproxy fronted" bound to a different port (e.g 1234) so no accessible from the outside and populate the backends according to consul tags, then in the bastion put in place a solution for resolving your chosen “haproxy_internal_domain” to a given slave so your interal services would be available in the bastion VPN via “app.haproxy_internal_domain:1234”. Other possibilty would be to expose a given weave subnetwork to the bastion so all the internal services would be accesible via consul DNS as in your case like *.service.consul. We are pending on https://github.com/weaveworks/weave/issues/117#issuecomment-124075671 so we can be more granular at the time of creating weave subnets.

tayzlor commented 9 years ago

Kinda Related https://github.com/Capgemini/Apollo/issues/122

enxebre commented 8 years ago

See posible solution here https://github.com/Capgemini/Apollo/pull/468