ExternalIP Address Assignments in Rancher 2.0 and Azure ACS


I currently have Rancher v2.0.0-alpha9 running against an Azure Container Service Kubernetes cluster.

From within the Rancher kubectl tool, here is the version info:

Client Version: version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.4”, GitCommit:“793658f2d7ca7f064d2bdf606519f9fe1229c381”, GitTreeState:“clean”, BuildDate:“2017-08-17T08:48:23Z”, GoVersion:“go1.8.3”, Compiler:“g
c”, Platform:“linux/amd64”}
Server Version: version.Info{Major:“1”, Minor:“7”, GitVersion:“v1.7.9”, GitCommit:“19fe91923d584c30bd6db5c5a21e9f0d5f742de8”, GitTreeState:“clean”, BuildDate:“2017-10-19T16:55:06Z”, GoVersion:“go1.8.3”, Compiler:“g
c”, Platform:“linux/amd64”}

I’m able to create a service with a container via the Rancher CLI, and create a port mapping. However, I can’t find any reference to the external IP that gets assigned to my service anywhere in my infrastructure.

How does Rancher assign the external ip of each host? Does it sound like this is related to using ACS as the underlying Kubernetes cluster?

Also, 2.0 looks great so far! Can’t wait for the beta!