Local IP for rancher agent with Scale Sets

Issues that I’m currently facing when working with auto scale sets… ;

  • When scaling down
    Hosts go into “reconnecting”-state, where I would expect a cleanup after a given period… Automatically remove disconnected hosts

  • When scaling up
    As I want to scale from 0 tot … I’m limited by the amount of public IP’s I can assign (in the case of Azure). So I want the inter host network to use the Azure internal networks and expose service via the load balancer. The caveat I have here is that I can only do this via the “CATTLE_AGENT_IP”. Suggestion : A “switch” (triggered by an environment variable) that would trigger the agent to use a local network interface instead of the source nat ip adress of the hosts. OR (more complex) extend the agent to work with NATted environments. As the main reason for the public IP address is due to the fact that port 500 & 4500 are not configurable.