Service - Static IP

[jaybee]

Hi,

I’m using Rancher and I’m really happy with it!

I’ve an orchestrator (x.x.x.155), and three nodes (x.x.x.156…158).
When I create a service, depending on the each node load, the container can be hosted in any node. When I restart the service for example, the host can change and its IP.
Let’s say I have one web application with the host/private port 80:80.
How can I set a static IP to link with a linked service?
Maybe my question seems stupid but I tried with a load balancer and it doesn’t work…

[alena]

@jaybee we don’t have static ip concept in Rancher today. There are a couple of workarounds to support your use case:

• pin service to deploy to a particular host by setting scheduling labels on the service. This way the service’s containers will get deployed only on particular host (or set of hosts)
• Use Rancher Route53 service which will publish Service FQDN to AWS Route53, and will manage host ips records for this fqdn based on the service’s deployment: http://rancher.com/introducing-rancher-service-discovery-integration-with-amazon-route53/