Rancher in Private Subnet?

I’ve setup a Rancher master inside a private subnet (AWS) This is accessible from my ip and seems to work fine.

I next tried to spin up a new host inside the same subnet, checked the [x] Use Private IP box and it times out waiting for SSH and then is terminated. I’ve also tried specifying the agent IP on master startup with CATTLE_AGENT_IP=

Given that these should be connecting with the private IP, I can’t see why they wouldn’t be accessible?

1 Like